Systems and methods for signaling tiles and slices in video coding

ABSTRACT

A method of encoding video data is disclosed. The method comprising: signaling a first syntax element specifying whether each subpicture consists of one and only one rectangular slice, or each subpicture consists of one or more rectangular slices; signaling a second syntax element specifying a number of rectangular slices in each picture referring to a picture parameter set in a case that the first syntax element specifies that each subpicture consists of one or more rectangular slices; determining whether or not a third syntax element is to be signaled based on the second syntax element; signaling the third syntax element, specifying whether or not fourth syntax elements are present in the picture parameter set, based on the second syntax element; and signaling the fourth syntax elements, specifying a difference in indexes between two rectangular slices, based on the second syntax element and the third syntax element.

TECHNICAL FIELD

This disclosure relates to video coding and more particularly to techniques for signaling tiles and slices for coded video.

BACKGROUND ART

Digital video capabilities can be incorporated into a wide range of devices, including digital televisions, laptop or desktop computers, tablet computers, digital recording devices, digital media players, video gaming devices, cellular telephones, including so-called smartphones, medical imaging devices, and the like. Digital video may be coded according to a video coding standard. Video coding standards define the format of a compliant bitstream encapsulating coded video data. A compliant bitstream is a data structure that may be received and decoded by a video decoding device to generate reconstructed video data. Video coding standards may incorporate video compression techniques. Examples of video coding standards include ISO/IEC MPEG-4 Visual and ITU-T H.264 (also known as ISO/IEC MPEG-4 AVC) and High-Efficiency Video Coding (HEVC). HEVC is described in High Efficiency Video Coding (HEVC), Rec. ITU-T H.265, December 2016, which is incorporated by reference, and referred to herein as ITU-T H.265. Extensions and improvements for ITU-T H.265 are currently being considered for the development of next generation video coding standards. For example, the ITU-T Video Coding Experts Group (VCEG) and ISO/IEC (Moving Picture Experts Group (MPEG) (collectively referred to as the Joint Video Exploration Team (JVET)) are working to standardized video coding technology with a compression capability that significantly exceeds that of the current HEVC standard. The Joint Exploration Model 7 (JEM 7), Algorithm Description of Joint Exploration Test Model 7 (JEM 7), ISO/IEC JTC1/SC29/WG11 Document: JVET-G1001, July 2017, Torino, IT, which is incorporated by reference herein, describes the coding features that were under coordinated test model study by the JVET as potentially enhancing video coding technology beyond the capabilities of ITU-T H.265. It should be noted that the coding features of JEM 7 are implemented in JEM reference software. As used herein, the term JEM may collectively refer to algorithms included in JEM 7 and implementations of JEM reference software. Further, in response to a “Joint Call for Proposals on Video Compression with Capabilities beyond HEVC,” jointly issued by VCEG and MPEG, multiple descriptions of video coding tools were proposed by various groups at the 10th Meeting of ISO/IEC JTC1/SC29/WG11 16-20 Apr. 2018, San Diego, Calif. From the multiple descriptions of video coding tools, a resulting initial draft text of a video coding specification is described in “Versatile Video Coding (Draft 1),” 10th Meeting of ISO/IEC JTC1/SC29/WG11 16-20 Apr. 2018, San Diego, Calif., document JVET-J1001-v2, which is incorporated by reference herein, and referred to as JVET-J1001. The current development of a next generation video coding standard by the VCEG and MPEG is referred to as the Versatile Video Coding (VVC) project. “Versatile Video Coding (Draft 7),” 16th Meeting of ISO/IEC JTC1/SC29/WG11 1-11 Oct. 2019, Geneva, CH, document JVET-P2001-vE, which is incorporated by reference herein, and referred to as JVET-P2001, represents the current iteration of the draft text of a video coding specification corresponding to the VVC project.

Video compression techniques enable data requirements for storing and transmitting video data to be reduced. Video compression techniques may reduce data requirements by exploiting the inherent redundancies in a video sequence. Video compression techniques may sub-divide a video sequence into successively smaller portions (i.e., groups of pictures within a video sequence, a picture within a group of pictures, regions within a picture, sub-regions within regions, etc.). Intra prediction coding techniques (e.g., spatial prediction techniques within a picture) and inter prediction techniques (i.e., inter-picture techniques (temporal)) may be used to generate difference values between a unit of video data to be coded and a reference unit of video data. The difference values may be referred to as residual data. Residual data may be coded as quantized transform coefficients. Syntax elements may relate residual data and a reference coding unit (e.g., intra-prediction mode indices, and motion information). Residual data and syntax elements may be entropy coded. Entropy encoded residual data and syntax elements may be included in data structures forming a compliant bitstream.

SUMMARY OF INVENTION

In one example, a method of encoding video data, the method comprising: signaling a first syntax element specifying whether each subpicture consists of one and only one rectangular slice, or each subpicture consists one or more rectangular slices; signaling a second syntax element specifying a number of rectangular slices in each picture referring to a picture parameter set in a case that the first syntax element specifies that each subpicture consists one or more rectangular slices; determining whether or not a third syntax element is to be signaled based on the second syntax element; signaling the third syntax element, specifying whether or not fourth syntax elements are present in the picture parameter set, based on the second syntax element; and signaling the fourth syntax elements, specifying a difference in indexes between two rectangular slices, based on the second syntax element and the third syntax element.

In one example, a method of decoding video data, the method comprising: decoding a first syntax element specifying whether each subpicture consists of one and only one rectangular slice, or each subpicture consists one or more rectangular slices; decoding a second syntax element specifying a number of rectangular slices in each picture referring to a picture parameter set in a case that the first syntax element specifies that each subpicture consists one or more rectangular slices; determining whether or not a third syntax element is to be decoded based on the second syntax element; decoding a third syntax element, specifying whether or not fourth syntax elements are present in the picture parameter set, based on the second syntax element; and decoding the fourth syntax elements, specifying a difference in indexes between two rectangular slices, based on the second syntax element and the third syntax element.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating an example of a system that may be configured to encode and decode video data according to one or more techniques of this this disclosure.

FIG. 2 is a conceptual diagram illustrating coded video data and corresponding data structures according to one or more techniques of this this disclosure.

FIG. 3 is a conceptual diagram illustrating a data structure encapsulating coded video data and corresponding metadata according to one or more techniques of this this disclosure.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of a system that may be configured to encode and decode video data according to one or more techniques of this this disclosure.

FIG. 5 is a block diagram illustrating an example of a video encoder that may be configured to encode video data according to one or more techniques of this disclosure.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure.

DESCRIPTION OF EMBODIMENTS

In general, this disclosure describes various techniques for coding video data. In particular, this disclosure describes techniques for signaling reference picture lists for coded video data. It should be noted that although techniques of this disclosure are described with respect to ITU-T H.264, ITU-T H.265, JEM, and JVET-P2001, the techniques of this disclosure are generally applicable to video coding. For example, the coding techniques described herein may be incorporated into video coding systems, (including video coding systems based on future video coding standards) including video block structures, intra prediction techniques, inter prediction techniques, transform techniques, filtering techniques, and/or entropy coding techniques other than those included in ITU-T H.265, JEM, and JVET-P2001. Thus, reference to ITU-T H.264, ITU-T H.265, JEM, and/or JVET-P2001 is for descriptive purposes and should not be construed to limit the scope of the techniques described herein. Further, it should be noted that incorporation by reference of documents herein is for descriptive purposes and should not be construed to limit or create ambiguity with respect to terms used herein. For example, in the case where an incorporated reference provides a different definition of a term than another incorporated reference and/or as the term is used herein, the term should be interpreted in a manner that broadly includes each respective definition and/or in a manner that includes each of the particular definitions in the alternative.

In one example, a method of signaling picture partitioning information for video data comprising signaling a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally signaling one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one example, a method of decoding video data comprises parsing a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally parsing one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one example, a device comprises one or more processors configured to signal a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally signal one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one example, a non-transitory computer-readable storage medium comprises instructions stored thereon that, when executed, cause one or more processors of a device to signal a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally signal one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one example, an apparatus comprises means for signaling a syntax element indicating whether each rectangular slice consists of exactly one tile and means for conditionally signaling one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one example, a device comprises one or more processors configured to parse a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally parse one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one example, a non-transitory computer-readable storage medium comprises instructions stored thereon that, when executed, cause one or more processors of a device to parse a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally parse one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one example, an apparatus comprises means for parsing a syntax element indicating whether each rectangular slice consists of exactly one tile and means for conditionally parsing one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

The details of one or more examples are set forth in the accompanying drawings and the description below. Other features, objects, and advantages will be apparent from the description and drawings, and from the claims.

Video content includes video sequences comprised of a series of frames (or pictures). A series of frames may also be referred to as a group of pictures (GOP). Each video frame or picture may divided into one or more regions. Regions may be defined according to a base unit (e.g., a video block) and sets of rules defining a region. For example, a rule defining a region may be that a region must be an integer number of video blocks arranged in a rectangle. Further, video blocks in a region may be ordered according to a scan pattern (e.g., a raster scan). As used herein, the term video block may generally refer to an area of a picture or may more specifically refer to the largest array of sample values that may be predictively coded, sub-divisions thereof, and/or corresponding structures. Further, the term current video block may refer to an area of a picture being encoded or decoded. A video block may be defined as an array of sample values. It should be noted that in some cases pixel values may be described as including sample values for respective components of video data, which may also be referred to as color components, (e.g., luma (Y) and chroma (Cb and Cr) components or red, green, and blue components). It should be noted that in some cases, the terms pixel value and sample value are used interchangeably. Further, in some cases, a pixel or sample may be referred to as a pel. A video sampling format, which may also be referred to as a chroma format, may define the number of chroma samples included in a video block with respect to the number of luma samples included in a video block. For example, for the 4:2:0 sampling format, the sampling rate for the luma component is twice that of the chroma components for both the horizontal and vertical directions.

A video encoder may perform predictive encoding on video blocks and sub-divisions thereof. Video blocks and sub-divisions thereof may be referred to as nodes. ITU-T H.264 specifies a macroblock including 16×16 luma samples. That is, in ITU-T H.264, a picture is segmented into macroblocks. ITU-T H.265 specifies an analogous Coding Tree Unit (CTU) structure (which may be referred to as a largest coding unit (LCU)). In ITU-T H.265, pictures are segmented into CTUs. In ITU-T H.265, for a picture, a CTU size may be set as including 16×16, 32×32, or 64×64 luma samples. In ITU-T H.265, a CTU is composed of respective Coding Tree Blocks (CTB) for each component of video data (e.g., luma (Y) and chroma (Cb and Cr). It should be noted that video having one luma component and the two corresponding chroma components may be described as having two channels, i.e., a luma channel and a chroma channel. Further, in ITU-T H.265, a CTU may be partitioned according to a quadtree (QT) partitioning structure, which results in the CTBs of the CTU being partitioned into Coding Blocks (CB). That is, in ITU-T H.265, a CTU may be partitioned into quadtree leaf nodes. According to ITU-T H.265, one luma CB together with two corresponding chroma CBs and associated syntax elements are referred to as a coding unit (CU). In ITU-T H.265, a minimum allowed size of a CB may be signaled. In ITU-T H.265, the smallest minimum allowed size of a luma CB is 8×8 luma samples. In ITU-T H.265, the decision to code a picture area using intra prediction or inter prediction is made at the CU level.

In ITU-T H.265, a CU is associated with a prediction unit structure having its root at the CU. In ITU-T H.265, prediction unit structures allow luma and chroma CBs to be split for purposes of generating corresponding reference samples. That is, in ITU-T H.265, luma and chroma CBs may be split into respective luma and chroma prediction blocks (PBs), where a PB includes a block of sample values for which the same prediction is applied. In ITU-T H.265, a CB may be partitioned into 1, 2, or 4 PBs. ITU-T H.265 supports PB sizes from 64×64 samples down to 4×4 samples. In ITU-T H.265, square PBs are supported for intra prediction, where a CB may form the PB or the CB may be split into four square PBs. In ITU-T H.265, in addition to the square PBs, rectangular PBs are supported for inter prediction, where a CB may by halved vertically or horizontally to form PBs. Further, it should be noted that in ITU-T H.265, for inter prediction, four asymmetric PB partitions are supported, where the CB is partitioned into two PBs at one quarter of the height (at the top or the bottom) or width (at the left or the right) of the CB. Intra prediction data (e.g., intra prediction mode syntax elements) or inter prediction data (e.g., motion data syntax elements) corresponding to a PB is used to produce reference and/or predicted sample values for the PB.

JEM specifies a CTU having a maximum size of 256×256 luma samples. JEM specifies a quadtree plus binary tree (QTBT) block structure. In JEM, the QTBT structure enables quadtree leaf nodes to be further partitioned by a binary tree (BT) structure. That is, in JEM, the binary tree structure enables quadtree leaf nodes to be recursively divided vertically or horizontally. In JVET-P2001, CTUs are partitioned according a quadtree plus multi-type tree (QTMT or QT+MTT) structure. The QTMT in JVET-P2001 is similar to the QTBT in JEM. However, in JVET-P2001, in addition to indicating binary splits, the multi-type tree may indicate so-called ternary (or triple tree (TT)) splits. A ternary split divides a block vertically or horizontally into three blocks. In the case of a vertical TT split, a block is divided at one quarter of its width from the left edge and at one quarter its width from the right edge and in the case of a horizontal TT split a block is at one quarter of its height from the top edge and at one quarter of its height from the bottom edge.

As described above, each video frame or picture may be divided into one or more regions. For example, according to ITU-T H.265, each video frame or picture may be partitioned to include one or more slices and further partitioned to include one or more tiles, where each slice includes a sequence of CTUs (e.g., in raster scan order) and where a tile is a sequence of CTUs corresponding to a rectangular area of a picture. It should be noted that a slice, in ITU-T H.265, is a sequence of one or more slice segments starting with an independent slice segment and containing all subsequent dependent slice segments (if any) that precede the next independent slice segment (if any). A slice segment, like a slice, is a sequence of CTUs. Thus, in some cases, the terms slice and slice segment may be used interchangeably to indicate a sequence of CTUs arranged in a raster scan order. Further, it should be noted that in ITU-T H.265, a tile may consist of CTUs contained in more than one slice and a slice may consist of CTUs contained in more than one tile. However, ITU-T H.265 provides that one or both of the following conditions shall be fulfilled: (1) All CTUs in a slice belong to the same tile; and (2) All CTUs in a tile belong to the same slice.

With respect to JVET-P2001, slices are required to consist of an integer number of complete tiles or an integer number of consecutive complete CTU rows within a tile, instead of only being required to consist of an integer number of CTUs. It should be noted that in JVET-P2001, the slice design does not include slice segments (i.e., no independent/dependent slice segments). Thus, in JVET-P2001, a picture may include a single tile, where the single tile is contained within a single slice or a picture may include multiple tiles where the multiple tiles (or CTU rows thereof) may be contained within one or more slices. In JVET-P2001, the partitioning of a picture into tiles is specified by specifying respective heights for tile rows and respective widths for tile columns. Thus, in JVET-P2001 a tile is a rectangular region of CTUs within a particular tile row and a particular tile column position. Further, it should be noted that JVET-P2001 provides where a picture may be partitioned into subpictures, where a subpicture is a rectangular region of a CTUs within a picture. The top-left CTU of a subpicture may be located at any CTU position within a picture with subpictures being constrained to include one or more slices Thus, unlike a tile, a subpicture is not necessarily limited to a particular row and column position. It should be noted that subpictures may be useful for encapsulating regions of interest within a picture and a subbitstream extraction process may be used to only decode and display a particular region of interest. That is, as described in further detail below, a bitstream of coded video data includes a sequence of network abstraction layer (NAL) units, where a NAL unit encapsulates coded video data, (i.e., video data corresponding to a slice of picture) or a NAL unit encapsulates metadata used for decoding video data (e.g., a parameter set) and a sub-bitstream extraction process forms a new bitstream by removing one or more NAL units from a bitstream.

FIG. 2 is a conceptual diagram illustrating an example of a picture within a group of pictures partitioned according to tiles, slices, and subpictures. It should be noted that the techniques described herein may be applicable to tiles, slices, subpictures, subdivisions thereof and/or equivalent structures thereto. That is, the techniques described herein may be generally applicable regardless of how a picture is partitioned into regions. For example, in some cases, the techniques described herein may be applicable in cases where a tile may be partitioned into so-called bricks, where a brick is a rectangular region of CTU rows within a particular tile. Further, for example, in some cases, the techniques described herein may be applicable in cases where one or more tiles may be included in so-called tile groups, where a tile group includes an integer number of adjacent tiles. In the example illustrated in FIG. 2 , Pic₃ is illustrated as including 16 tiles (i.e., Tile₀ to Tile₁₅) and three slices (i.e., Slice₀ to Slice₂). In the example illustrated in FIG. 2 , Slice₀ includes four tiles (i.e., Tile₀ to Tile₃), Slice₁ includes eight tiles (i.e., Tile₄ to Tile₁₁), and Slice₂ includes four tiles (i.e., Tile₁₂ to Tile₁₅). Further, as illustrated in the example of FIG. 2 , Pic₃ is illustrated as including two subpictures (i.e., Subpicture₀ and Subpicture₁), where Subpicture₀ includes Slice₀ and Slice₁ and where Subpicture₁ includes Slice₂. As described above, subpictures may be useful for encapsulating regions of interest within a picture and a sub-bitstream extraction process may be used in order to selectively decode (and display) a region interest. For example, referring to FIG. 2 , Subpicture₀ may corresponding to an action portion of a sporting event presentation (e.g., a view of the field) and Subpicture₁ may corresponding to a scrolling banner displayed during the sporting event presentation. By using organizing a picture into subpictures in this manner, a viewer may be able to disable the display of the scrolling banner. That is, through a sub-bitstream extraction process Slice₂ NAL unit may be removed from a bitstream (and thus not decoded and/or displayed) and Slice₀ NAL unit and Slice₁ NAL unit may be decoded and displayed. The encapsulation of slices of a picture into respective NAL unit data structures and sub-bitstream extraction are described in further detail below.

For intra prediction coding, an intra prediction mode may specify the location of reference samples within a picture. In ITU-T H.265, defined possible intra prediction modes include a planar (i.e., surface fitting) prediction mode, a DC (i.e., flat overall averaging) prediction mode, and 33 angular prediction modes (predMode: 2-34). In JEM, defined possible intra-prediction modes include a planar prediction mode, a DC prediction mode, and 65 angular prediction modes. It should be noted that planar and DC prediction modes may be referred to as non-directional prediction modes and that angular prediction modes may be referred to as directional prediction modes. It should be noted that the techniques described herein may be generally applicable regardless of the number of defined possible prediction modes.

For inter prediction coding, a reference picture is determined and a motion vector (MV) identifies samples in the reference picture that are used to generate a prediction for a current video block. For example, a current video block may be predicted using reference sample values located in one or more previously coded picture(s) and a motion vector is used to indicate the location of the reference block relative to the current video block. A motion vector may describe, for example, a horizontal displacement component of the motion vector (i.e., MV_(x)), a vertical displacement component of the motion vector (i.e., MV_(y)), and a resolution for the motion vector (e.g., one-quarter pixel precision, one-half pixel precision, one-pixel precision, two-pixel precision, four-pixel precision). Previously decoded pictures, which may include pictures output before or after a current picture, may be organized into one or more to reference pictures lists and identified using a reference picture index value. Further, in inter prediction coding, uni-prediction refers to generating a prediction using sample values from a single reference picture and bi-prediction refers to generating a prediction using respective sample values from two reference pictures. That is, in uni-prediction, a single reference picture and corresponding motion vector are used to generate a prediction for a current video block and in bi-prediction, a first reference picture and corresponding first motion vector and a second reference picture and corresponding second motion vector are used to generate a prediction for a current video block. In bi-prediction, respective sample values are combined (e.g., added, rounded, and clipped, or averaged according to weights) to generate a prediction. Pictures and regions thereof may be classified based on which types of prediction modes may be utilized for encoding video blocks thereof. That is, for regions having a B type (e.g., a B slice), bi-prediction, uni-prediction, and intra prediction modes may be utilized, for regions having a P type (e.g., a P slice), uni-prediction, and intra prediction modes may be utilized, and for regions having an I type (e.g., an I slice), only intra prediction modes may be utilized. As described above, reference pictures are identified through reference indices. For example, for a P slice, there may be a single reference picture list, RefPicList0 and for a B slice, there may be a second independent reference picture list, RefPicList1, in addition to RefPicList0. It should be noted that for uni-prediction in a B slice, one of RefPicList0 or RefPicList1 may be used to generate a prediction. Further, it should be noted that during the decoding process, at the onset of decoding a picture, reference picture list(s) are generated from previously decoded pictures stored in a decoded picture buffer (DPB).

Further, a coding standard may support various modes of motion vector prediction. Motion vector prediction enables the value of a motion vector for a current video block to be derived based on another motion vector. For example, a set of candidate blocks having associated motion information may be derived from spatial neighboring blocks and temporal neighboring blocks to the current video block. Further, generated (or default) motion information may be used for motion vector prediction. Examples of motion vector prediction include advanced motion vector prediction (AMVP), temporal motion vector prediction (TMVP), so-called “merge” mode, and “skip” and “direct” motion inference. Further, other examples of motion vector prediction include advanced temporal motion vector prediction (ATMVP) and Spatial-temporal motion vector prediction (STMVP). For motion vector prediction, both a video encoder and video decoder perform the same process to derive a set of candidates. Thus, for a current video block, the same set of candidates is generated during encoding and decoding.

As described above, for inter prediction coding, reference samples in a previously coded picture are used for coding video blocks in a current picture. Previously coded pictures which are available for use as reference when coding a current picture are referred as reference pictures. It should be noted that the decoding order does not necessary correspond with the picture output order, i.e., the temporal order of pictures in a video sequence. In ITU-T H.265, when a picture is decoded it is stored to a decoded picture buffer (DPB) (which may be referred to as frame buffer, a reference buffer, a reference picture buffer, or the like). In ITU-T H.265, pictures stored to the DPB are removed from the DPB when they been output and are no longer needed for coding subsequent pictures. In ITU-T H.265, a determination of whether pictures should be removed from the DPB is invoked once per picture, after decoding a slice header, i.e., at the onset of decoding a picture. For example, referring to FIG. 2 , Pic₁ is illustrated as referencing Pic₁. Similarly, Pic₃ is illustrated as referencing Pic₀. With respect to FIG. 2 , assuming the picture number corresponds to the decoding order, the DPB would be populated as follows: after decoding Pic₀, the DPB would include {Pic₀}; at the onset of decoding Pic₁, the DPB would include {Pic₀}; after decoding Pic₁, the DPB would include {Pic₀, Pic₁}; at the onset of decoding Pic₂, the DPB would include {Pic₀, Pic₁}. Pic₂ would then be decoded with reference to Pic₁ and after decoding Pic₂, the DPB would include {Pic₀, Pic₁, Pic₂}. At the onset of decoding Pic₃, pictures Pic₀ and Pic₁ would be marked for removal from the DPB, as they are not needed for decoding Pic₃ (or any subsequent pictures, not shown) and assuming Pic₁ and Pic₂ have been output, the DPB would be updated to include {Pic₀}. Pic₃ would then be decoded by referencing Pic₀. The process of marking pictures for removal from a DPB may be referred to as reference picture set (RPS) management.

As described above, intra prediction data or inter prediction data is used to produce reference sample values for a block of sample values. The difference between sample values included in a current PB, or another type of picture area structure, and associated reference samples (e.g., those generated using a prediction) may be referred to as residual data. Residual data may include respective arrays of difference values corresponding to each component of video data. Residual data may be in the pixel domain. A transform, such as, a discrete cosine transform (DCT), a discrete sine transform (DST), an integer transform, a wavelet transform, or a conceptually similar transform, may be applied to an array of difference values to generate transform coefficients. It should be noted that in ITU-T H.265 and JVET-P2001, a CU is associated with a transform tree structure having its root at the CU level. The transform tree is partitioned into one or more transform units (TUs). That is, an array of difference values may be partitioned for purposes of generating transform coefficients (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values). For each component of video data, such sub-divisions of difference values may be referred to as Transform Blocks (TBs). It should be noted that in some cases, a core transform and a subsequent secondary transforms may be applied (in the video encoder) to generate transform coefficients. For a video decoder, the order of transforms is reversed.

A quantization process may be performed on transform coefficients or residual sample values directly (e.g., in the case, of palette coding quantization). Quantization approximates transform coefficients by amplitudes restricted to a set of specified values. Quantization essentially scales transform coefficients in order to vary the amount of data required to represent a group of transform coefficients. Quantization may include division of transform coefficients (or values resulting from the addition of an offset value to transform coefficients) by a quantization scaling factor and any associated rounding functions (e.g., rounding to the nearest integer). Quantized transform coefficients may be referred to as coefficient level values. Inverse quantization (or “dequantization”) may include multiplication of coefficient level values by the quantization scaling factor, and any reciprocal rounding or offset addition operations. It should be noted that as used herein the term quantization process in some instances may refer to division by a scaling factor to generate level values and multiplication by a scaling factor to recover transform coefficients in some instances. That is, a quantization process may refer to quantization in some cases and inverse quantization in some cases. Further, it should be noted that although in some of the examples below quantization processes are described with respect to arithmetic operations associated with decimal notation, such descriptions are for illustrative purposes and should not be construed as limiting. For example, the techniques described herein may be implemented in a device using binary operations and the like. For example, multiplication and division operations described herein may be implemented using bit shifting operations and the like.

Quantized transform coefficients and syntax elements (e.g., syntax elements indicating a coding structure for a video block) may be entropy coded according to an entropy coding technique. An entropy coding process includes coding values of syntax elements using lossless data compression algorithms. Examples of entropy coding techniques include content adaptive variable length coding (CAVLC), context adaptive binary arithmetic coding (CABAC), probability interval partitioning entropy coding (PIPE), and the like. Entropy encoded quantized transform coefficients and corresponding entropy encoded syntax elements may form a compliant bitstream that can be used to reproduce video data at a video decoder. An entropy coding process, for example, CABAC, may include performing a binarization on syntax elements. Binarization refers to the process of converting a value of a syntax element into a series of one or more bits. These bits may be referred to as “bins.” Binarization may include one or a combination of the following coding techniques: fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding. For example, binarization may include representing the integer value of 5 for a syntax element as 00000101 using an 8-bit fixed length binarization technique or representing the integer value of 5 as 11110 using a unary coding binarization technique. As used herein each of the terms fixed length coding, unary coding, truncated unary coding, truncated Rice coding, Golomb coding, k-th order exponential Golomb coding, and Golomb-Rice coding may refer to general implementations of these techniques and/or more specific implementations of these coding techniques. For example, a Golomb-Rice coding implementation may be specifically defined according to a video coding standard. In the example of CABAC, for a particular bin, a context provides a most probable state (MPS) value for the bin (i.e., an MPS for a bin is one of 0 or 1) and a probability value of the bin being the MPS or the least probably state (LPS). For example, a context may indicate, that the MPS of a bin is 0 and the probability of the bin being 1 is 0.3. It should be noted that a context may be determined based on values of previously coded bins including bins in the current syntax element and previously coded syntax elements. For example, values of syntax elements associated with neighboring video blocks may be used to determine a context for a current bin.

With respect to the equations used herein, the following arithmetic operators may be used:

-   -   + Addition     -   − Subtraction     -   * Multiplication, including matrix multiplication     -   x^(y) Exponentiation. Specifies x to the power of y. In other         contexts, such notation is used for superscripting not intended         for interpretation as exponentiation.     -   / Integer division with truncation of the result toward zero.         For example, 7/4 and −7/−4 are truncated to 1 and −7/4 and 7/−4         are truncated to     -   ÷ Used to denote division in mathematical equations where no         truncation or rounding is intended.

$\frac{x}{y}$

-   -    Used to denote division in mathematical equations where no         truncation or rounding is intended.

Further, the following mathematical functions may be used:

-   -   Log 2(x) the base-2 logarithm of x;

${{Min}\left( {x,y} \right)} = \left\{ {\begin{matrix} x & ; & {x<=\overset{.}{y}} \\ y & ; & {x > y} \end{matrix};} \right.$ ${{Max}\left( {x,y} \right)} = \left\{ \begin{matrix} x & ; & {x>=y} \\ y & ; & {x < y} \end{matrix} \right.$

-   -   Ceil(x) the smallest integer greater than or equal to x.

With respect to the example syntax used herein, the following definitions of logical operators may be applied:

-   -   x && y Boolean logical “and” of x and y     -   x∥y Boolean logical “or” of x and y     -   ! Boolean logical “not”     -   x?y: z If x is TRUE or not equal to 0, evaluates to the value of         y; otherwise, evaluates to the value of z.

Further, the following relational operators may be applied:

-   -   > Greater than     -   >= Greater than or equal to     -   < Less than     -   <= Less than or equal to     -   == Equal to     -   != Not equal to

Further, it should be noted that in the syntax descriptors used herein, the following descriptors may be applied:

-   -   b(8): byte having any pattern of bit string (8 bits). The         parsing process for this descriptor is specified by the return         value of the function read_bits(8).     -   f(n): fixed-pattern bit string using n bits written (from left         to right) with the left bit first. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n).     -   se(v): signed integer 0-th order Exp-Golomb-coded syntax element         with the left bit first.     -   tb(v): truncated binary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   tu(v): truncated unary using up to maxVal bits with maxVal         defined in the semantics of the symtax element.     -   u(n): unsigned integer using n bits. When n is “v” in the syntax         table, the number of bits varies in a manner dependent on the         value of other syntax elements. The parsing process for this         descriptor is specified by the return value of the function         read_bits(n) interpreted as a binary representation of an         unsigned integer with most significant bit written first.     -   ue(v): unsigned integer 0-th order Exp-Golomb-coded syntax         element with the left bit first.

As described above, video content includes video sequences comprised of a series of pictures and each picture may be divided into one or more regions. In JVET-P2001, a coded representation of a picture is referred to as a coded picture and all CTUs of the coded picture are encapsulated in one or more coded slice NAL units. That is, one or more corresponding coded slice NAL units encapsulate a coded representation of a picture. For example, referring again to FIG. 2 , the coded representation of Pic₃ is encapsulated in three coded slice NAL units (i.e., Slice₀ NAL unit, Slice₁ NAL unit, and Slice₂ NAL unit). It should be noted that the term video coding layer (VCL) NAL unit is used as a collective term for coded slice NAL units, i.e., VCL NAL is a collective term which includes all types of slice NAL units. As described above, and in further detail below, a NAL unit may encapsulate metadata used for decoding video data. A NAL unit encapsulating metadata used for decoding a video sequence is generally referred to as a non-VCL NAL unit. Thus, in JVET-P2001, a NAL unit may be a VCL NAL unit or a non-VCL NAL unit. It should be noted that a VCL NAL unit includes slice header data, which provides information used for decoding the particular slice. Thus, in JVET-P2001, information used for decoding video data, which may be referred to as metadata in some cases, is not limited to being included in non-VCL NAL units. JVET-P2001 provides where a picture unit (PU) is a set of NAL units that contain all VCL NAL units of a coded picture and their associated non-VCL NAL units and where an access unit (AU) is a set of NAL units that are associated with each other according to a specified classification rule, are consecutive in decoding order, and contain exactly one coded picture for each present picture unit. A PU consists of one picture header NAL unit, one coded picture, which comprises of one or more VCL NAL units, and zero or more non-VCL NAL units. Thus, in JVET-P2001 an access unit includes one or more coded pictures. In some cases, an access unit may include pictures included in different layers of video. Layers of video are described in further detail below. Further, in JVET-P2001, a coded video sequence (CVS) is a sequence of AUs that consists, in decoding order, of a CVSS AU, followed by zero or more AUs that are not CVSS AUs, including all subsequent AUs up to but not including any subsequent AU that is a CVSS AU, where a coded video sequence start (CVSS) AU is an AU in which there is a picture unit for each layer in the CVS and the coded picture in each present picture unit is a coded layer video sequence start (CLVSS) picture. In JVET-P2001, a coded layer video sequence (CLVS) is a sequence of PUs within the same layer that consists, in decoding order, of a CLVSS PU, followed by zero or more PUs that are not CLVSS PUs, including all subsequent PUs up to but not including any subsequent PU that is a CLVSS PU. This is, in JVET-P2001, a bitstream may be described as including a sequence of NAL units forming a CVS, where a CVS includes AUs and each AU may include respective pictures for each of a plurality of layers for coded video.

Multi-layer video coding enables a video presentation to be decoded/displayed as a presentation corresponding to a base layer of video data and decoded/displayed one or more additional presentations corresponding to enhancement layers of video data. For example, a base layer may enable a video presentation having a basic level of quality (e.g., a High Definition rendering and/or a 30 Hz frame rate) to be presented and an enhancement layer may enable a video presentation having an enhanced level of quality (e.g., an Ultra High Definition rendering and/or a 60 Hz frame rate) to be presented. An enhancement layer may be coded by referencing a base layer. That is, for example, a picture in an enhancement layer may be coded (e.g., using inter-layer prediction techniques) by referencing one or more pictures (including scaled versions thereof) in a base layer. It should be noted that layers may also be coded independent of each other. In this case, there may not be inter-layer prediction between two layers. Each NAL unit may include an identifier indicating a layer of video data the NAL unit is associated with. As described above, a sub-bitstream extraction process may be used to only decode and display a particular region of interest of a picture. Further, a sub-bitstream extraction process may be used to only decode and display a particular layer of video. Sub-bitstream extraction may refer to a process where a device receiving a compliant or conforming bitstream forms a new compliant or conforming bitstream by discarding and/or modifying data in the received bitstream. For example, sub-bitstream extraction may be used to form a new compliant or conforming bitstream corresponding to a particular representation of video (e.g., a high quality representation).

In JVET-P2001, each of a video sequence, a GOP, a picture, a slice, and CTU may be associated with metadata that describes video coding properties and some types of metadata an encapsulated in non-VCL NAL units. JVET-P2001 defines parameters sets that may be used to describe video data and/or video coding properties. In particular, JVET-P2001 includes the following five types of parameter sets: decoding parameter set (DPS), video parameter set (VPS), sequence parameter set (SPS), picture parameter set (PPS), and adaption parameter set (APS), where a SPS applies to apply to zero or more entire CVSs, a PPS applies to zero or more entire coded pictures, a APS applies to zero or more slices, and a DPS and a VPS may be optionally referenced by a SPS. A PPS applies to an individual coded picture that refers to it. In JVET-P2001, parameter sets may be encapsulated as a non-VCL NAL unit and/or may be signaled as a message. JVET-P2001 also includes a picture header (PH) which is encapsulated as a non-VCL NAL unit. In JVET-P2001, a picture header applies to all slices of a coded picture. JVET-P2001 further enables supplemental enhancement information (SEI) messages to be signaled. In JVET-P2001, SEI messages assist in processes related to decoding, display or other purposes, however, SEI messages may not be required for constructing the luma or chroma samples according to a decoding process. In JVET-P2001, SEI messages may be signaled in a bitstream using non-VCL NAL units. Further, SEI messages may be conveyed by some mechanism other than by being present in the bitstream (i.e., signaled out-of-band).

FIG. 3 illustrates an example of a bitstream including multiple CVSs, where a CVS includes AUs, and AUs include picture units. The example illustrated in FIG. 3 corresponds to an example of encapsulating the slice NAL units illustrated in the example of FIG. 2 in a bitstream. In the example illustrated in FIG. 3 , the corresponding picture unit for Pic₃ includes the three VCL NAL coded slice NAL units, i.e., Slice₀ NAL unit, Slice₁ NAL unit, and Slice₂ NAL unit and two non-VCL NAL units, i.e., a PPS NAL Unit and a PH NAL unit. It should be noted that in FIG. 3 , HEADER is a NAL unit header (i.e., not to be confused with a slice header). Further, it should be noted that in FIG. 3 , other non-VCL NAL units, which are not illustrated may be included in the CVSs, e.g., SPS NAL units, VPS NAL units, SEI message NAL units, etc. Further, it should be noted that in other examples, a PPS NAL Unit used for decoding Pic₃ may be included elsewhere in the bitstream, e.g., in the picture unit corresponding to Pic₀ or may be provided by an external mechanism. However, it should be note that in JVET-P2001, the picture header for each picture is required to be in the picture unit corresponding to the picture.

As provided in above, in JVET-P2001, a picture may include multiple tiles where the multiple tiles (or CTU rows thereof) may be contained within one or more slices and the partitioning of a picture into tiles is specified by specifying respective heights for tile rows and respective widths for tile columns. in JVET-P2001 the picture parameter set syntax structure provides information specifying how a picture is partitioned into tiles and slices. Table 1 illustrates the relevant portion of the syntax structure of the picture parameter set syntax provided in JVET-P2001 for specifying how a picture is partitioned into tiles and slices.

TABLE 1 Descriptor pic_parameter_set_rbsp( ) {  pps_pic_parameter_set_id ue(v)  pps_seq_parameter_set_id u(4)  pic_width_in_luma_samples ue(v)  pic_height_in_luma_samples ue(v)  conformance_window_flag u(1)  if( conformance_window_flag ) {   conf_win_left_offset ue(v)   conf_win_right_offset ue(v)   conf_win_top_offset ue(v)   conf_win_bottom_offset ue(v)  }  scaling_window_flag u(1)  if( scaling_window_flag ) {   scaling_win_left_offset ue(v)   scaling_win_right_offset ue(v)   scaling_win_top_offset ue(v)   scaling_win_bottom_offset ue(v)  }  output_flag_present_flag u(1)  mixed_nalu_types_in_pic_flag u(1)  pps_subpic_id_signalling_present_flag u(1)  if( pps_subpics_id_signalling_present_flag ) {   pps_num_subpics_minus1 ue(v)   pps_subpic_id_len_minus1 ue(v)   for( i = 0; i <= pps_num_subpic_minus1; i++ )    pps_subpic_id[ i ] u(v)  }  no_pic_partition_flag u(1)  if( !no_pic_partition_flag ) {   pps_log2_ctu_size_minus5 u(2)   num_exp_tile_columns_minus1 ue(v)   num_exp_tile_rows_minus1 ue(v)   for( i = 0; i <= num_exp_tile_columns_minus1; i++ )    tile_column_width_minus1[ i ] ue(v)   for( i = 0; i <= num_exp_tile_rows_minus1; i++ )    tile_row_height_minus1[ i ] ue(v)   rect_slice_flag u(1)   if( rect_slice_flag)    single_slice_per_subpic_flag u(1)   if( rect_slice_flag && !single_slice_per_subpic_flag ) {    num_slices_in_pic_minus1 ue(v)    tile_idx_delta_present_flag u(1)    for( i = 0; i < num_slices_in_pic_minus1; i++ ) {     slice_width_in_tiles_minus1[ i ] ue(v)     slice_height_in_tiles_minus1[ i ] ue(v)     if( slice_width_in_tiles_minus1[ i ] == 0 &&        slice_height_in_tiles_minus1[ i ] == 0 ) {      num_slices_in_tile_minus1[ i ] ue(v)      numSlicesInTileMinus1 = num_slices_in_tile_ minus1[ i ]      for(j = 0; j < numSlicesInTileMinus1;j+ )       slice_height_in_ctu_minus1[ i++ ] ue(v)     }     if( tile_idx_delta_present_flag && i < num_ slices_in_pic_minus1 )      tile_idx_delta[ i ] se(v)    }   }   loop_filter_across_tiles_enabled_flag u(1)   loop_filter_across_slices_enabled_flag u(1)  }  entropy_coding_sync_enabled_flag u(1)  if( !no_pic_partition_flag | | entropy_coding_sync_enabled_flag )   entry point offsets present flag u(1)  ... u(1) }

With respect to Table 1, JVET-P2001 provides the following semantics:

A PPS RBSP shall be available to the decoding process prior to it being referenced, included in at least one AU with Temporand less than or equal to the Temporand of the PPS NAL unit or provided through external means.

All PPS NAL units with a particular value of pps_pic_parameter_set_id within a PU shall have the same content.

pps_pic_parameter_set_id identifies the PPS for reference by other syntax elements. The value of pps_pic_parameter_set_id shall be in the range of 0 to 63, inclusive.

PPS NAL units, regardless of the nuh_layer_id values, share the same value space of pps_pic_parameter_set_id.

pps_seq_parameter_set_id specifies the value of sps_seq_parameter_set_id for the SPS. The value of pps_seq_parameter_set_id shall be in the range of 0 to 15, inclusive. The value of pps_seq_parameter_set_id shall be the same in all PPSs that are referred to by coded pictures in a CLVS.

pic_width_in_luma_samples specifies the width of each decoded picture referring to the PPS in units of luma samples. pic_width_in_luma_samples shall not be equal to 0, shall be an integer multiple of Max(8, MinCbSizeY), and shall be less than or equal to pic_width_max_in_luma_samples.

When subpics_present_flag is equal to 1 or ref_pic_resampling_enabled_flag equal to 0, the value of pic_width_in_luma_samples shall be equal to pic_width_max_in_luma_samples.

pic_height_in_luma_samples specifies the height of each decoded picture referring to the PPS in units of luma samples. pic_height_in_luma_samples shall not be equal to 0 and shall be an integer multiple of Max(8, MinCbSizeY), and shall be less than or equal to pic_height_max_in_luma_samples.

When subpics_present_flag is equal to 1 or ref_pic_resampling_enabled_flag equal to 0, the value of pic_height_in_luma_samples shall be equal to pic_height_max_in_luma_samples.

Let refPicWidthInLumaSamples and refPicHeightInLumaSamples be the pic_width_in_luma_samples and pic height in luma samples, respectively, of a reference picture of a current picture referring to this PPS. Is a requirement of bitstream conformance that all of the following conditions are satisfied:

-   -   pic_width_in_luma_samples*2 shall be greater than or equal to         refPicWidthInLumaSamples.     -   pic_height_in_luma_samples*2 shall be greater than or equal to         refPicHeightInLumaSamples.     -   pic_width_in_luma_samples shall be less than or equal to         refPicWidthInLumaSamples*8.     -   pic_height_in_luma_samples shall be less than or equal to         refPicHeightInLumaSamples*8.         The variables PicWidthInCtbsY, PicHeightInCtbsY, PicSizeInCtbsY,         PicWidthInMinCbsY, PicHeightInMinCbsY, PicSizeInMinCbsY,         PicSizeInSamplesY, PicWidthInSamplesC and PicHeightInSamplesC         are derived as follows:

PicWidthInCtbsY=Ceil(pic_width_in_luma_samples÷CtbSizeY)

PicHeightInCtbsY=Ceil(pic_height_in_luma_samples÷CtbSizeY)

PicSizeInCtbsY=PicWidthInCtbsY*PicHeightInCtbsY

PicWidthInMinCbsY=pic_width_in_luma_samples/MinCbSizeY

PicHeightInMinCbsY=pic_height_in_luma_samples/MinCbSizeY

PicSizeInMinCbsY=PicWidthInMinCbsY*PicHeightInMinCbsY

PicSizeInSamplesY=pic_width_in_luma_samples*pic_height_in_luma_samples

PicWidthInSamplesC=pic_width_in_luma_samples/SubWidthC

PicHeightInSamplesC=pic_height_in_luma_samples/SubHeightC

conformance_window_flag equal to 1 indicates that the conformance cropping window offset parameters follow next in the PPS. conformance_window_flag equal to 0 indicates that the conformance cropping window offset parameters are not present. conf_win_left_offset, conf_win_right_offset, conf_win_top_offset, and conf_win_bottom_offset specify the samples of the pictures in the CLVS that are output from the decoding process, in terms of a rectangular region specified in picture coordinates for output. When conformance_window_flag is equal to 0, the values of conf_win_left_offset, conf_win_right_offset, conf_win_top_offset, and conf_win_bottom_offset are inferred to be equal to 0. The conformance cropping window contains the luma samples with horizontal picture coordinates from SubWidthC*conf_win_left_offset to pic_width_in_luma_samples−(SubWidthC conf_win_right_offset+1) and vertical picture coordinates from SubHeightC*conf_win_top_offset to pic_height_in_luma_samples−(SubHeightC*conf_win_bottom_offset+1), inclusive. The value of SubWidthC (conf_win_left_offset+conf_win_right_offset) shall be less than pic width in luma samples, and the value of SubHeightC (conf_win_top_offset+conf_win_bottom_offset) shall be less than pic_height_in_luma_samples. When ChromaArrayType is not equal to 0, the corresponding specified samples of the two chroma arrays are the samples having picture coordinates (x/SubWidthC, y/SubHeightC), where (x, y) are the picture coordinates of the specified luma samples.

-   -   NOTE—The conformance cropping window offset parameters are only         applied at the output. All internal decoding processes are         applied to the uncropped picture size.         Let ppsA and ppsB be any two PPSs referring to the same SPS. It         is a requirement of bitstream conformance that, when ppsA and         ppsB have the same the values of pic_width_in_luma_samples and         pic height in luma samples, respectively, ppsA and ppsB shall         have the same values of conf_win_left_offset,         conf_win_right_offset, conf_win_top_offset, and         conf_win_bottom_offset, respectively.         scaling_window_flag equal to 1 specifies that the scaling window         offset parameters are present in the PPS. scaling_window_flag         equal to 0 specifies that the scaling window offset parameters         are not present in the PPS. When ref_pic_resampling_enabled_flag         is equal to 0, the value of scaling_window_flag shall be equal         to 0. scaling_win_left_offset, scaling_win_right_offset,         scaling_win_top_offset, and scaling_win_bottom_offset specify         the offsets, in units of luma samples, that are applied to the         picture size for scaling ratio calculation. When         scaling_window_flag is equal to 0, the values of         scaling_win_left_offset, scaling_win_right_offset,         scaling_win_top_offset, and scaling_win_bottom_offset are         inferred to be equal to 0. The value of         scaling_win_left_offset+scaling_win_right_offset shall be less         than pic width in luma samples, and the value of         scaling_win_top_offset+scaling_win_bottom_offset shall be less         than pic_height_in_luma_samples. The variables PicOutputWidthL         and PicOutputHeightL are derived as follows:

PicOutputWidthL=pic_width_in_luma_samples−(scaling_win_right_offset+scaling_win_left_offset)

PicOutputHeightL=pic_height_in_luma_samples−(scaling_win_bottom_offset+scaling_win_top_offset)

output_flag_present_flag equal to 1 indicates that the pic output flag syntax element is present in slice headers referring to the PPS. output_flag_present_flag equal to 0 indicates that the pic_output_flag syntax element is not present in slice headers referring to the PPS. mixed_nalu_types_in_pic_flag equal to 1 specifies that each picture referring to the PPS has more than one VCL NAL unit and that the VCL NAL units do not have the same value of nal_unit_type and that the picture is not an TRAP picture. mixed_nalu_types_in_pic_flag equal to 0 specifies that each picture referring to the PPS has one or more VCL NAL units and the VCL NAL units of each picture referring to the PPS have the same value of nal_unit_type. When no_mixed_nalu_types_in_pic_constraint_flag is equal to 1, the value of mixed_nalu_types_in_pic_flag shall be equal to 0. For each slice with a nal_unit_type value nalUnitTypeA in the range of IDR_W_RADL to CRA_NUT, inclusive, in a picture picA that also contains one or more slices with another value of nal_unit_type (i.e., the value of mixed_nalu_types_in_pic_flag for the picture picA is equal to 1), the following applies:

-   -   The slice shall belong to a subpicture subpicA for which the         value of the corresponding subpic_treated_as_pic_flag[i] is         equal to 1.     -   The slice shall not belong to a subpicture of picA containing         VCL NAL units with nal_unit_type not equal to nalUnitTypeA.     -   For all the following PUs in the CLVS in decoding order, neither         RefPicList[0] nor RefPicList[1] of a slice in subpicA shall         include any picture preceding picA in decoding order in an         active entry.         pps_subpic_id_signalling_present_flag equal to 1 specifies that         subpicture ID mapping is signalled in the PPS.         pps_subpic_id_signalling_present_flag equal to 0 specifies that         subpicture ID mapping is not signalled in the PPS. When         sps_subpic_id_present_flag is 0 or         sps_subpic_id_signalling_present_flag is equal to 1,         pps_subpic_id_signalling_present_flag shall be equal to 0.         pps_num_subpics_minus1 plus 1 specifies the number of         subpictures in the coded pictures referring to the PPS.         It is a requirement of bitstream conformance that the value of         pps_num_subpic_minus1 shall be equal to sps_num_subpics_minus1.         pps_subpic_id_len_minus1 plus 1 specifies the number of bits         used to represent the syntax element pps_subpic_id[i]. The value         of pps_subpic_id_len_minus1 shall be in the range of 0 to 15,         inclusive.         It is a requirement of bitstream conformance that the value of         pps_subpic_id_len_minus1 shall be the same for all PPSs that are         referred to by coded pictures in a CLVS.         pps_subpic_id[i] specifies the subpicture ID of the i-th         subpicture. The length of the pps_subpic_id[i] syntax element is         pps_subpic_id_len_minus1+1 bits. no_pic_partition_flag equal to         1 specifies that no picture partitioning applied to each picture         referring to the PPS. no_pic_partition_flag equal to 0 specifies         each picture referring to the PPS may be partitioned into more         than one tile or slice.         It is a requirement of bitstream conformance that the value of         no_pic_partition_flag shall be the same for all PPSs that are         referred to by coded pictures within a CLVS.         It is a requirement of bitstream conformance that the value of         no_pic_partition_flag shall not be equal to 1 when the value of         sps_num_subpics_minus1+1 is greater than 1.         pps_log2_ctu_size_minus5 plus 5 specifies the luma coding tree         block size of each CTU. pps_log2_ctu_size_minus5 shall be equal         to sps_log2_ctu_size_minus5. num_exp_tile_columns_minus1 plus 1         specifies the number of explicitly provided tile column widths.         The value of num_exp_tile_columns_minus1 shall be in the range         of 0 to PicWidthInCtbsY−1, inclusive. When no_pic_partition_flag         is equal to 1, the value of num_exp_tile_columns_minus1 is         inferred to be equal to 0.         num_exp_tile_rows_minus1 plus 1 specifies the number of         explicitly provided tile row heights. The value of         num_exp_tile_rows_minus1 shall be in the range of 0 to         PicHeightInCtbsY−1, inclusive. When no_pic_partition_flag is         equal to 1, the value of num_tile_rows_minus1 is inferred to be         equal to 0.         tile_column_width_minus1[i] plus 1 specifies the width of the         i-th tile column in units of CTBs for i in the range of 0 to         num_exp_tile_columns_minus1−1, inclusive.         tile_column_width_minus1[num_exp_tile_columns_minus1] is used to         derive the width of the tile columns with index greater than or         equal to num_exp_tile_columns_minus1 as specified below. When         not present, the value of tile_column_width_minus1[0] is         inferred to be equal to PicWidthInCtbsY−1.         tile_row_height_minus1[i] plus 1 specifies the height of the         i-th tile row in units of CTBs for i in the range of 0 to         num_exp_tile_rows_minus1−1, inclusive.         tile_row_height_minus1[num_exp_tile_rows_minus1] is used to         derive the height of the tile rows with index greater than or         equal to num_exp_tile_rows_minus1 as specified below. When not         present, the value of tile_row_height_minus1[0] is inferred to         be equal to PicHeightInCtbsY−1.         rect_slice_flag equal to 0 specifies that tiles within each         slice are in raster scan order and the slice information is not         signalled in PPS. rect_slice_flag equal to 1 specifies that         tiles within each slice cover a rectangular region of the         picture and the slice information is signalled in the PPS. When         not present, rect_slice_flag is inferred to be equal to 1. When         subpics_present_flag is equal to 1, the value of rect_slice_flag         shall be equal to 1.         single_slice_per_subpic_flag equal to 1 specifies that each         subpicture consists of one and only one rectangular slice.         single_slice_per_subpic_flag equal to 0 specifies that each         subpicture may consist one or more rectangular slices. When         subpics_present_flag is equal to 0, single_slice_per_subpic_flag         shall be equal to 0.         When single_slice_per_subpic_flag is equal to 1,         num_slices_in_pic_minus1 is inferred to be equal to         sps_num_subpics_minus1.         num_slices_in_pic_minus1 plus 1 specifies the number of         rectangular slices in each picture referring to the PPS. The         value of num_slices_in_pic_minus1 shall be in the range of 0 to         MaxSlicesPerPicture−1, inclusive, where MaxSlicesPerPicture is         specified. When no_pic_partition_flag is equal to 1, the value         of num_slices_in_pic_minus1 is inferred to be equal to 0.         tile_idx_delta_present_flag equal to 0 specifies that         tile_idx_delta values are not present in the PPS and that all         rectangular slices in pictures referring to the PPS are         specified in raster order according to the process defined in         below.         tile_idx_delta_present_flag equal to 1 specifies that         tile_idx_delta values may be present in the PPS and that all         rectangular slices in pictures referring to the PPS are         specified in the order indicated by the values of         tile_idx_delta.         slice_width_in_tiles_minus1[i] plus 1 specifies the width of the         i-th rectangular slice in units of tile columns. The value of         slice_width_in_tiles_minus1[i] shall be in the range of 0 to         NumTileColumns−1, inclusive. When not present, the value of         slice_width_in_tiles_minus1[i] is inferred as specified below.         slice_height_in_tiles_minus1[i] plus 1 specifies the height of         the i-th rectangular slice in units of tile rows. The value of         slice_height_in_tiles_minus1[i] shall be in the range of 0 to         NumTileRows−1, inclusive. When not present, the value of         slice_height_in_tiles_minus1[i] is inferred as specified below.         num_slices_in_tile_minus1[i] plus 1 specifies the number of         slices in the current tile for the case where the i-th slice         contains a subset of CTU rows from a single tile. The value of         num_slices_in_tile_minus1[i] shall be in the range of 0 to         RowHeight[tileY]−1, inclusive, where tileY is the tile row index         containing the i-th slice. When not present, the value of         num_slices_in_tile_minus1[i] is inferred to be equal to 0.         slice_height_in_ctu_minus1[i] plus 1 specifies the height of the         i-th rectangular slice in units of CTU rows for the case where         the i-th slice contains a subset of CTU rows from a single tile.         The value of slice_height_in_ctu_minus1[i] shall be in the range         of 0 to RowHeight[tileY]−1, inclusive, where tileY is the tile         row index containing the i-th slice.         tile_idx_delta[i] specifies the difference in tile index between         the i-th rectangular slice and the (i+1)-th rectangular slice.         The value of tile_idx_delta[i] shall be in the range of         −NumTilesInPic+1 to NumTilesInPic−1, inclusive. When not         present, the value of tile_idx_delta[i] is inferred to be equal         to 0. In all other cases, the value of tile_idx_delta[i] shall         not be equal to 0.         loop_filter_across_tiles_enabled_flag equal to 1 specifies that         in-loop filtering operations may be performed across tile         boundaries in pictures referring to the PPS.         loop_filter_across_tiles_enabled_flag equal to 0 specifies that         in-loop filtering operations are not performed across tile         boundaries in pictures referring to the PPS. The in-loop         filtering operations include the deblocking filter, sample         adaptive offset filter, and adaptive loop filter operations.         When not present, the value of         loop_filter_across_tiles_enabled_flag is inferred to be equal to         1.         loop_filter_across_slices_enabled_flag equal to 1 specifies that         in-loop filtering operations may be performed across slice         boundaries in pictures referring to the PPS. loop filter across         slice enabled flag equal to 0 specifies that in-loop filtering         operations are not performed across slice boundaries in pictures         referring to the PPS. The in-loop filtering operations include         the deblocking filter, sample adaptive offset filter, and         adaptive loop filter operations. When not present, the value of         loop_filter_across_slices_enabled_flag is inferred to be equal         to 0.         entropy_coding_sync_enabled_flag equal to 1 specifies that a         specific synchronization process for context variables is         invoked before decoding the CTU that includes the first CTB of a         row of CTBs in each tile in each picture referring to the PPS,         and a specific storage process for context variables is invoked         after decoding the CTU that includes the first CTB of a row of         CTBs in each tile in each picture referring to the PPS.         entropy_coding_sync_enabled_flag equal to 0 specifies that no         specific synchronization process for context variables is         required to be invoked before decoding the CTU that includes the         first CTB of a row of CTBs in each tile in each picture         referring to the PPS, and no specific storage process for         context variables is required to be invoked after decoding the         CTU that includes the first CTB of a row of CTBs in each tile in         each picture referring to the PPS.         It is a requirement of bitstream conformance that the value of         entropy_coding_sync_enabled_flag shall be the same for all PPSs         that are referred to by coded pictures within a CLVS.         When entry point offsets present flag is equal to 1, the         variable NumEntryPoints, which specifies the number of entry         points in the current slice, is derived as follows:

NumEntryPoints = 0 for( i = 1; i < NumCtuInCurrSlice; i++ ) {  CtbAddrInRs = CtbAddrInCurrSlice[ i ]  CtbAddrX = ( CtbAddrInRs % PicWidthlnCtbsY )  CtbAddrY = ( CtbAddrInRs / PicWidthlnCtbsY )  if( CtbAddrX = = CtbToTileColBd[ CtbAddrX ] &&   ( CtbAddrY = = CtbToTileRowBd[ CtbAddrY ] | | entropy_coding_sync_enabled_flag ) )   NumEntryPoints++ }

JVET-P2001 processes for CTB raster scanning, tile scanning, and subpicture scanning:

-   -   The variable NumTileColumns, specifying the number of tile         columns, and the list colWidth[i] for i ranging from 0 to         NumTileColumn−1, inclusive, specifying the width of the i-th         tile column in units of CTBs, are derived as follows:

remainingWidthInCtbsY = PicWidthInCtbsY for( i = 0; i < num_exp_tile_columns_minus1; i++ ) {  colWidth[ i ] = tile_column_width_minus1[ i ] + 1  remainingWidthInCtbsY −= colWidth[ i ] } uniformTile ColWidth = tile_column_width_minus1[ num_exp_tile_columns_minus1 ] + 1 while( remainingWidthInCtbsY >= uniformTileColWidth ) {  colWidth[ i++ ] = uniformTileColWidth  remainingWidthInCtbsY −= uniformTileColWidth } if( remainingWidthInCtbsY > 0 )  colWidth[ i++ ] = remainingWidthInCtbsY NumTileColumns = i

-   -   The variable NumTileRows, specifying the number of tile rows,         and the list RowHeight[j] for j ranging from 0 to NumTileRows−1,         inclusive, specifying the height of the j-th tile row in units         of CTBs, are derived as follows:

remainingHeightInCtbsY = PicHeightInCtbsY for( j = 0; j < num_exp_tile_rows_minus1; j++ ) {  RowHeight[ j ] = tile_row_height_minus1[ j ] + 1  remainingHeightInCtbsY −= RowHeight[ j ] } uniformTileRowHeight = tile_row_height_minus1[ num_exp_tile_rows_minus1 ] + 1 while( remainingHeightInCtbsY >= uniformTileRowHeight ) {  RowHeight[ j++ ] = uniformTileRowHeight  remainingHeightInCtbsY −= uniformTileRowHeight if( remainingHeightInCtbsY > 0 )  RowHeight[ j++ ] = remainingHeightInCtbsY NumTileRows = j

-   -   The variable NumTilesInPic is set equal to         NumTileColumns*NumTileRows.     -   The list tileColBd[i] for i ranging from 0 to NumTileColumns,         inclusive, specifying the location of the i-th tile column         boundary in units of CTBs, is derived as follows:         -   for(tileColBd[0]=0, i=0; i<NumTileColumns; i++)             tileColBd[i+1]=tileColBd[i]+colWidth[i]     -   The list tileRowBd[j] for j ranging from 0 to NumTileRows,         inclusive, specifying the location of the j-th tile row boundary         in units of CTBs, is derived as follows:         -   for(tileRowBd[0]=0, j=0; j<NumTileRows; j++)             tileRowBd[j+1]=tileRowBd[j]+RowHeight[j]     -   The list CtbToTileColBd[ctbAddrX] for ctbAddrX ranging from 0 to         PicWidthInCtbsY, inclusive, specifying the conversion from a         horizontal CTB address to a left tile column boundary in units         of CTBs, is derived as follows:

tileX = 0 for( ctbAddrX = 0; ctbAddrX <= PicWidthlnCtbsY; ctbAddrX++ ) {  if( ctbAddrX = = tileColBd[ tileX + 1 ] )   tileX++  CtbToTileColBd[ ctbAddrX ] = tileColBd[ tileX ] }

-   -   The list CtbToTileRowBd[ctbAddrY] for ctbAddrY ranging from 0 to         PicHeightInCtbsY, inclusive, specifying the conversion from a         vertical CTB address to a top tile column boundary in units of         CTBs, is derived as follows:

tileY = 0 for( ctbAddrY = 0; ctbAddrY <= PicHeightInCtbsY; ctbAddrY++ ) {  if( ctbAddrY = = tileRowBd[ tileY + 1 ] )  CtbToTileRowBd[ ctbAddrY ] = tileRowBd[ tileY ] }

-   -   For rectangular slices, the list NumCtuInSlice[i] for i ranging         from 0 to num_slices_in_pic_minus1, inclusive, specifying the         number of CTU in the i-th slice, and the matrix         CtbAddrInSlice[i][j] for i ranging from 0 to         num_slices_in_pic_minus1, inclusive, and j ranging from 0 to         NumCtuInSlice[i]−1, inclusive, specifying the picture raster         scan address of the j-th CTB within the i-th slice, are derived         as follows:

if( subpics_present_flag && single_slice_per_subpic_flag ) {  for( i = 0; i <= sps_num_subpics_minus1; i++ )   NumCtuInSlice[ i ] = 0  for( i = 0; i < PicSizelnCtbsY; i ++ ) {   sliceIdx = CtbToSubPicIdx[ i ]   CtbAddrInSlice[ sliceIdx ][ NumCtuInSlice[ sliceIdx ] ] = i   NumCtuInSlice[ sliceIdx ]++  } } else {  tileIdx = 0  for( i = 0; i <= num_slices_in_pic_minus1; i++ )   NumCtuInSlice[ i ] = 0  for( i = 0; i <= num_slices_in_pic_minus1; i++ ) {   tileX = tileIdx % NumTileColumns   tileY = tileIdx / NumTileColumns   if( i = = num_slices_in_pic_minus 1 ) {    slice_width_in_tiles_minus1[ i ] = NumTileColumns − 1 − tileX    slice_height_in_tiles_minus1[ i ] = NumTileRows − 1 − tileY    num_slices_in_tile_minus1[ i ] = 0   }   if( slice_width_in_tiles_minus1[ i ] = = 0 && slice_height_in_tiles_minus1[ i ] = = 0){    ctbY = tileRowBd[ tileY ]    numSlicesInTileMinus1 = num_slices_in_tile_minus1[ i ]    for( j = 0; j < numSlicesInTileMinus1; j++ ) {     AddCtbsToSlice( i, tileColBd[ tileX ], tileColBd[ tileX + 1 ],      ctbY, ctbY + slice_height_in_ctu_minus1[ i ] + 1 )     ctbY += slice_height_in_ctu_minus1[ i ] + 1     i++    }    AddCtbsToSlice( i, tileColBd[ tileX ], tileColBd[ tileX + 1 ], ctbY, tileRowBd[ tileY + 1 ] )   } else    for( j = 0; j <= slice_height_in_tiles_minus1[ i ]; j++ )     for( k = 0; k <= slice_width_in_tiles_minus1[ i ]; k++ )      AddCtbsToSlice( i, tileColBd[ tileX + k ], tileColBd[ tileX + k + 1 ],       tileRowBd[ tileY + j ], tileRowBd[ tileY + j + 1 ] )   if( tile_idx_delta_present_flag )    tileIdx += tile_idx_delta[ i ]   else {    tileIdx += slice_width_in_tiles_minus1[ i ] + 1    if( tileIdx % NumTileColumns = = 0 )     tileIdx += slice_height_in_tiles_minus1[ i ]* NumTileColumns   }  } }

-   -   Where the function AddCtbsToSlice(sliceIdx, startX, stopX,         startY, stopY) is specified as follows:

for( ctbY = start Y; ctbY < stopY; ctbY++ )  for( ctbX = startX; ctbX < stopX; ctbX++ ) {   CtbAddrInSlice[ sliceIdx ][ NumCtuInSlice[ sliceIdx ] ] = ctbY * PicWidthInCtbsY + ctbX   NumCtuInSlice[ sliceIdx ]++  }

-   -   It is a requirement of bitstream conformance that the values of         NumCtuInSlice[i] for i ranging from 0 to         num_slices_in_pic_minus1, inclusive, shall be greater than 0.         Additionally, it is a requirement of bitstream conformance that         the matrix CtbAddrInSlice[i][j] for i ranging from 0 to         num_slices_in_pic_minus1, inclusive, and j ranging from 0 to         NumCtuInSlice[i]−1, inclusive, shall include all CTB addresses         in the range 0 to PicSizeInCtbsY−1 once and only once.     -   The list CtbToSubPicIdx[ctbAddrRs] for ctbAddrRs ranging from 0         to PicSizeInCtbsY−1, inclusive, specifying the conversion from a         CTB address in picture raster scan to a subpicture index, is         derived as follows:

for( ctbAddrRs = 0; ctbAddrRs < PicSizeInCtbsY; ctbAddrRs++ ) {  posX = ctbAddrRs % PicWidthInCtbsY * CtbSizeY  posY = ctbAddrRs / PicWidthInCtbsY * CtbSizeY  CtbToSubPicIdx[ ctbAddrRs ] = − 1  for( i = 0; CtbToSubPicIdx[ ctbAddrRs ] < 0 && i <= sps_num_subpics_minus1; i++ ) {    (31)   if( (posX >= subpic_ctu_top_left_x[ i ] * CtbSizeY ) &&     ( posX < ( subpic_ctu_top_left_x[ i ] + subpic_width_minus1[ i ] + 1) * CtbSizeY ) &&     ( posY >= subpic_ctu_top _left_y[ i ] * CtbSizeY ) &&     ( posY < ( subpic_ctu_top_left_y[ i ] + subpic_height_minus1[ i ] + 1 ) * CtbSizeY ) )    CtbToSubPicIdx[ ctbAddrRs ] = i  } }

-   -   The list NumSlicesInSubpic[i] and SliceSubpicToPicIdx[i][k],         specifying the number of rectangular slices in the i-th         subpicture and picture-level slice index of the k-th slice in         the i-th subpicture, are derived is derived as follows:

for( j = 0; j <= sps_num_subpics_minus1; i++ )  NumSlicesInSubpic[ j ] = 0 for( i = 0; i <= num_slices_in_pic_minus1; i++ ) {  posX = CtbAddrInSlice[ i ][ 0 ] % PicWidthInCtbsY * CtbSizeY  posY = CtbAddrInSlice[ i ][ 0 ] / PicWidthInCtbsY * CtbSizeY  for( j = 0; j <= sps_num_subpics_minus1; i++ ) {   if( ( posX >= subpic_ctu_top_left_x[ j ] * CtbSizeY ) &&     ( posX < ( subpic_ctu_top_left_x[ j ] + subpic_width_minus1[ j ] + 1 ) * CtbSizeY ) &&     ( posY >= subpic_ctu_top_left_y[ j ] * CtbSizeY) &&     ( posY < ( subpic_ctu_top_left_y[ j ] + subpic_height_minus1[ j ] + 1 ) * CtbSizeY ) ) {    SliceSubpicToPicIdx[ j ][ NumSlicesInSubpic[ j ] ] = i    NumSlicesInSubpic[ j ]++   }  } }

The signaling of tiles and slices provided in JVET-P2001 may be less than ideal. In particular, for example, one or more tile and slice syntax elements in the PPS provided in JVET-P2001 may be signaled unnecessarily. Such signaling may be less than ideal. According to the techniques herein, one or more tile and slice syntax elements in the PPS, may be conditionally signaled and have an inferred value when not signaled.

FIG. 1 is a block diagram illustrating an example of a system that may be configured to code (i.e., encode and/or decode) video data according to one or more techniques of this disclosure. System 100 represents an example of a system that may encapsulate video data according to one or more techniques of this disclosure. As illustrated in FIG. 1 , system 100 includes source device 102, communications medium 110, and destination device 120. In the example illustrated in FIG. 1 , source device 102 may include any device configured to encode video data and transmit encoded video data to communications medium 110. Destination device 120 may include any device configured to receive encoded video data via communications medium 110 and to decode encoded video data. Source device 102 and/or destination device 120 may include computing devices equipped for wired and/or wireless communications and may include, for example, set top boxes, digital video recorders, televisions, desktop, laptop or tablet computers, gaming consoles, medical imagining devices, and mobile devices, including, for example, smartphones, cellular telephones, personal gaming devices.

Communications medium 110 may include any combination of wireless and wired communication media, and/or storage devices. Communications medium 110 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Communications medium 110 may include one or more networks. For example, communications medium 110 may include a network configured to enable access to the World Wide Web, for example, the Internet. A network may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Digital Video Broadcasting (DVB) standards, Advanced Television Systems Committee (ATSC) standards, Integrated Services Digital Broadcasting (ISDB) standards, Data Over Cable Service Interface Specification (DOCSIS) standards, Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3rd Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, Internet Protocol (IP) standards, Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards.

Storage devices may include any type of device or storage medium capable of storing data. A storage medium may include a tangible or non-transitory computer-readable media. A computer readable medium may include optical discs, flash memory, magnetic memory, or any other suitable digital storage media. In some examples, a memory device or portions thereof may be described as non-volatile memory and in other examples portions of memory devices may be described as volatile memory. Examples of volatile memories may include random access memories (RAM), dynamic random access memories (DRAM), and static random access memories (SRAM). Examples of non-volatile memories may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable memories (EPROM) or electrically erasable and programmable (EEPROM) memories. Storage device(s) may include memory cards (e.g., a Secure Digital (SD) memory card), internal/external hard disk drives, and/or internal/external solid state drives. Data may be stored on a storage device according to a defined file format.

FIG. 4 is a conceptual drawing illustrating an example of components that may be included in an implementation of system 100. In the example implementation illustrated in FIG. 4 , system 100 includes one or more computing devices 402A-402N, television service network 404, television service provider site 406, wide area network 408, local area network 410, and one or more content provider sites 412A-412N. The implementation illustrated in FIG. 4 represents an example of a system that may be configured to allow digital media content, such as, for example, a movie, a live sporting event, etc., and data and applications and media presentations associated therewith to be distributed to and accessed by a plurality of computing devices, such as computing devices 402A-402N. In the example illustrated in FIG. 4 , computing devices 402A-402N may include any device configured to receive data from one or more of television service network 404, wide area network 408, and/or local area network 410. For example, computing devices 402A-402N may be equipped for wired and/or wireless communications and may be configured to receive services through one or more data channels and may include televisions, including so-called smart televisions, set top boxes, and digital video recorders. Further, computing devices 402A-402N may include desktop, laptop, or tablet computers, gaming consoles, mobile devices, including, for example, “smart” phones, cellular telephones, and personal gaming devices.

Television service network 404 is an example of a network configured to enable digital media content, which may include television services, to be distributed. For example, television service network 404 may include public over-the-air television networks, public or subscription-based satellite television service provider networks, and public or subscription-based cable television provider networks and/or over the top or Internet service providers. It should be noted that although in some examples television service network 404 may primarily be used to enable television services to be provided, television service network 404 may also enable other types of data and services to be provided according to any combination of the telecommunication protocols described herein. Further, it should be noted that in some examples, television service network 404 may enable two-way communications between television service provider site 406 and one or more of computing devices 402A-402N. Television service network 404 may comprise any combination of wireless and/or wired communication media. Television service network 404 may include coaxial cables, fiber optic cables, twisted pair cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. Television service network 404 may operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include DVB standards, ATSC standards, ISDB standards, DTMB standards, DMB standards, Data Over Cable Service Interface Specification (DOCSIS) standards, HbbTV standards, W3C standards, and UPnP standards.

Referring again to FIG. 4 , television service provider site 406 may be configured to distribute television service via television service network 404. For example, television service provider site 406 may include one or more broadcast stations, a cable television provider, or a satellite television provider, or an Internet-based television provider. For example, television service provider site 406 may be configured to receive a transmission including television programming through a satellite uplink/downlink. Further, as illustrated in FIG. 4 , television service provider site 406 may be in communication with wide area network 408 and may be configured to receive data from content provider sites 412A-412N. It should be noted that in some examples, television service provider site 406 may include a television studio and content may originate therefrom.

Wide area network 408 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Telecommunications protocols may include proprietary aspects and/or may include standardized telecommunication protocols. Examples of standardized telecommunications protocols include Global System Mobile Communications (GSM) standards, code division multiple access (CDMA) standards, 3^(rd) Generation Partnership Project (3GPP) standards, European Telecommunications Standards Institute (ETSI) standards, European standards (EN), IP standards, Wireless Application Protocol (WAP) standards, and Institute of Electrical and Electronics Engineers (IEEE) standards, such as, for example, one or more of the IEEE 802 standards (e.g., Wi-Fi). Wide area network 408 may comprise any combination of wireless and/or wired communication media. Wide area network 408 may include coaxial cables, fiber optic cables, twisted pair cables, Ethernet cables, wireless transmitters and receivers, routers, switches, repeaters, base stations, or any other equipment that may be useful to facilitate communications between various devices and sites. In one example, wide area network 408 may include the Internet. Local area network 410 may include a packet based network and operate according to a combination of one or more telecommunication protocols. Local area network 410 may be distinguished from wide area network 408 based on levels of access and/or physical infrastructure. For example, local area network 410 may include a secure home network.

Referring again to FIG. 4 , content provider sites 412A-412N represent examples of sites that may provide multimedia content to television service provider site 406 and/or computing devices 402A-402N. For example, a content provider site may include a studio having one or more studio content servers configured to provide multimedia files and/or streams to television service provider site 406. In one example, content provider sites 412A-412N may be configured to provide multimedia content using the IP suite. For example, a content provider site may be configured to provide multimedia content to a receiver device according to Real Time Streaming Protocol (RTSP), HTTP, or the like. Further, content provider sites 412A-412N may be configured to provide data, including hypertext based content, and the like, to one or more of receiver devices computing devices 402A-402N and/or television service provider site 406 through wide area network 408. Content provider sites 412A-412N may include one or more web servers. Data provided by data provider site 412A-412N may be defined according to data formats.

Referring again to FIG. 1 , source device 102 includes video source 104, video encoder 106, data encapsulator 107, and interface 108. Video source 104 may include any device configured to capture and/or store video data. For example, video source 104 may include a video camera and a storage device operably coupled thereto. Video encoder 106 may include any device configured to receive video data and generate a compliant bitstream representing the video data. A compliant bitstream may refer to a bitstream that a video decoder can receive and reproduce video data therefrom. Aspects of a compliant bitstream may be defined according to a video coding standard. When generating a compliant bitstream video encoder 106 may compress video data. Compression may be lossy (discernible or indiscernible to a viewer) or lossless. FIG. 5 is a block diagram illustrating an example of video encoder 500 that may implement the techniques for encoding video data described herein. It should be noted that although example video encoder 500 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video encoder 500 and/or sub-components thereof to a particular hardware or software architecture. Functions of video encoder 500 may be realized using any combination of hardware, firmware, and/or software implementations.

Video encoder 500 may perform intra prediction coding and inter prediction coding of picture areas, and, as such, may be referred to as a hybrid video encoder. In the example illustrated in FIG. 5 , video encoder 500 receives source video blocks. In some examples, source video blocks may include areas of picture that has been divided according to a coding structure. For example, source video data may include macroblocks, CTUs, CBs, sub-divisions thereof, and/or another equivalent coding unit. In some examples, video encoder 500 may be configured to perform additional subdivisions of source video blocks. It should be noted that the techniques described herein are generally applicable to video coding, regardless of how source video data is partitioned prior to and/or during encoding. In the example illustrated in FIG. 5 , video encoder 500 includes summer 502, transform coefficient generator 504, coefficient quantization unit 506, inverse quantization and transform coefficient processing unit 508, summer 510, intra prediction processing unit 512, inter prediction processing unit 514, filter unit 516, and entropy encoding unit 518. As illustrated in FIG. 5 , video encoder 500 receives source video blocks and outputs a bitstream.

In the example illustrated in FIG. 5 , video encoder 500 may generate residual data by subtracting a predictive video block from a source video block. The selection of a predictive video block is described in detail below. Summer 502 represents a component configured to perform this subtraction operation. In one example, the subtraction of video blocks occurs in the pixel domain. Transform coefficient generator 504 applies a transform, such as a discrete cosine transform (DCT), a discrete sine transform (DST), or a conceptually similar transform, to the residual block or subdivisions thereof (e.g., four 8×8 transforms may be applied to a 16×16 array of residual values) to produce a set of residual transform coefficients. Transform coefficient generator 504 may be configured to perform any and all combinations of the transforms included in the family of discrete trigonometric transforms, including approximations thereof. Transform coefficient generator 504 may output transform coefficients to coefficient quantization unit 506. Coefficient quantization unit 506 may be configured to perform quantization of the transform coefficients. The quantization process may reduce the bit depth associated with some or all of the coefficients. The degree of quantization may alter the rate-distortion (i.e., bit-rate vs. quality of video) of encoded video data. The degree of quantization may be modified by adjusting a quantization parameter (QP). A quantization parameter may be determined based on slice level values and/or CU level values (e.g., CU delta QP values). QP data may include any data used to determine a QP for quantizing a particular set of transform coefficients. As illustrated in FIG. 5 , quantized transform coefficients (which may be referred to as level values) are output to inverse quantization and transform coefficient processing unit 508. Inverse quantization and transform coefficient processing unit 508 may be configured to apply an inverse quantization and an inverse transformation to generate reconstructed residual data. As illustrated in FIG. 5 , at summer 510, reconstructed residual data may be added to a predictive video block. In this manner, an encoded video block may be reconstructed and the resulting reconstructed video block may be used to evaluate the encoding quality for a given prediction, transformation, and/or quantization. Video encoder 500 may be configured to perform multiple coding passes (e.g., perform encoding while varying one or more of a prediction, transformation parameters, and quantization parameters). The rate-distortion of a bitstream or other system parameters may be optimized based on evaluation of reconstructed video blocks. Further, reconstructed video blocks may be stored and used as reference for predicting subsequent blocks.

Referring again to FIG. 5 , intra prediction processing unit 512 may be configured to select an intra prediction mode for a video block to be coded. Intra prediction processing unit 512 may be configured to evaluate a frame and determine an intra prediction mode to use to encode a current block. As described above, possible intra prediction modes may include planar prediction modes, DC prediction modes, and angular prediction modes. Further, it should be noted that in some examples, a prediction mode for a chroma component may be inferred from a prediction mode for a luma prediction mode. Intra prediction processing unit 512 may select an intra prediction mode after performing one or more coding passes. Further, in one example, intra prediction processing unit 512 may select a prediction mode based on a rate-distortion analysis. As illustrated in FIG. 5 , intra prediction processing unit 512 outputs intra prediction data (e.g., syntax elements) to entropy encoding unit 518 and transform coefficient generator 504. As described above, a transform performed on residual data may be mode dependent (e.g., a secondary transform matrix may be determined based on a predication mode).

Referring again to FIG. 5 , inter prediction processing unit 514 may be configured to perform inter prediction coding for a current video block. Inter prediction processing unit 514 may be configured to receive source video blocks and calculate a motion vector for PUs of a video block. A motion vector may indicate the displacement of a prediction unit of a video block within a current video frame relative to a predictive block within a reference frame. Inter prediction coding may use one or more reference pictures. Further, motion prediction may be uni-predictive (use one motion vector) or bi-predictive (use two motion vectors). Inter prediction processing unit 514 may be configured to select a predictive block by calculating a pixel difference determined by, for example, sum of absolute difference (SAD), sum of square difference (SSD), or other difference metrics. As described above, a motion vector may be determined and specified according to motion vector prediction. Inter prediction processing unit 514 may be configured to perform motion vector prediction, as described above. Inter prediction processing unit 514 may be configured to generate a predictive block using the motion prediction data. For example, inter prediction processing unit 514 may locate a predictive video block within a frame buffer (not shown in FIG. 5 ). It should be noted that inter prediction processing unit 514 may further be configured to apply one or more interpolation filters to a reconstructed residual block to calculate sub-integer pixel values for use in motion estimation. Inter prediction processing unit 514 may output motion prediction data for a calculated motion vector to entropy encoding unit 518.

Referring again to FIG. 5 , filter unit 516 receives reconstructed video blocks and coding parameters and outputs modified reconstructed video data. Filter unit 516 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering. SAO filtering is a non-linear amplitude mapping that may be used to improve reconstruction by adding an offset to reconstructed video data. It should be noted that as illustrated in FIG. 5 , intra prediction processing unit 512 and inter prediction processing unit 514 may receive modified reconstructed video block via filter unit 216. Entropy encoding unit 518 receives quantized transform coefficients and predictive syntax data (i.e., intra prediction data and motion prediction data). It should be noted that in some examples, coefficient quantization unit 506 may perform a scan of a matrix including quantized transform coefficients before the coefficients are output to entropy encoding unit 518. In other examples, entropy encoding unit 518 may perform a scan. Entropy encoding unit 518 may be configured to perform entropy encoding according to one or more of the techniques described herein. In this manner, video encoder 500 represents an example of a device configured to generate encoded video data according to one or more techniques of this disclosure.

Referring again to FIG. 1 , data encapsulator 107 may receive encoded video data and generate a compliant bitstream, e.g., a sequence of NAL units according to a defined data structure. A device receiving a compliant bitstream can reproduce video data therefrom. Further, as described above, sub-bitstream extraction may refer to a process where a device receiving a ITU-T H.265 compliant bitstream forms a new ITU-T H.265 compliant bitstream by discarding and/or modifying data in the received bitstream. It should be noted that the term conforming bitstream may be used in place of the term compliant bitstream. In one example, data encapsulator 107 may be configured to generate syntax according to one or more techniques described herein. It should be noted that data encapsulator 107 need not necessary be located in the same physical device as video encoder 106. For example, functions described as being performed by video encoder 106 and data encapsulator 107 may be distributed among devices illustrated in FIG. 4 .

As described above, the signaling of tiles and slices provided in JVET-P2001 may be less than ideal. In one example, according to the techniques herein, syntax element tile_idx_delta_present_flag may be conditionally signaled based on the value of num_slices_in_pic_minus1. It should be noted that it is necessary to signal tile_idx_delta_present_flag only when num_slices_in_pic_minus1 is greater than 0. Not signaling a syntax and inferring it instead, in this case, saves a bit. Table 2 illustrates an example of the relevant portion of the syntax structure of a picture parameter set syntax structure where syntax element tile_idx_delta_present_flag is conditionally signaled based on the value of num_slices_in_pic_minus1, according to the techniques herein.

TABLE 2 Descriptor pic_paramcter_set_rbsp( ) {  pps_pic_parameter_set_id ue(v)  pps_seq_parameter_set_id u(4)  pps_seq_parameter_set_id ue(v)  pic_width_in_luma_samples ue(v)  pic_height_in_luma_samples ue(v)  conformance_window_flag u(1)  if( conformance_window_flag ) {   conf_win_left_offset ue(v)   conf_win_right_offset ue(v)   conf_win_top_offset ue(v)   conf_win_bottom_offset ue(v)  }  scaling_window_flag u(1)  if( scaling_window_flag ) {   scaling_win_left_offset ue(v)   scaling_win_right_offset ue(v)   scaling_win_top_offset ue(v)   scaling_win_bottom_offset ue(v)  }  output_flag_present_flag u(1)  mixed_nalu_types_in_pic_flag u(1)  pps_subpic_id_signalling_present_flag u(1)  if( pps_subpics_id_signalling_present_flag ) {   pps_num_subpics_minus1 ue(v)   pps_subpic_id_len_minus1 ue(v)   for( i = 0; i <= pps_num_subpic_minus1; i++ )    pps_subpic_id[ i ] u(v)  }  no_pic_partition_flag u(1)  if( !no_pic_partition_flag ) {   pps_log2_ctu_size_minus5 u(2)   num_exp_tile_columns_minus1 ue(v)   num_exp_tile_rows_minus1 ue(v)   for( i = 0; i <= num_exp_tile_columns_minus1; i++ )    tile_column_width_minus1[ i ] ue(v)   for(i = 0; i <= num_exp_tile_rows_minus1; i++ )    tile_row_height_minus1[ i ] ue(v)   rect_slice_flag u(1)   if( rect_slice_flag )    single_slice_per_subpic_flag u(1)   if( rect_slice flag && !single_slice_per_subpic_flag ) {    num_slices_in_pic_minus1 ue(v)      if(num_slices_in_pic_minus1>0 )     tile_idx_delta_present_flag u(1)    for( i = 0; i < num_slices_in_pic_minus1; i++) {     slice_width_in_tiles_minus1[ i ] ue(v)     slice_height_in_tiles_minus1[ i ] ue(v)     if( slice_width_in_tiles_minus 1 [ i ]  == 0 &&      slice_height_in_tiles_minus1[ i ] == 0 ) {      num_slices_in_tile_minus1[ i ] ue(v)      numSlicesInTileMinus1 = num_slices_in_tile_ minus1[ i ]      for(j = 0; j < numSlicesInTileMinus1; j++ )       slice_height_m_ctu_minus1[ i++ ] ue(v)      }      if( tile_idx_delta_present_flag && i < num_slices_ in_pic_minus1 )       tile_idx_delta[ i ] se(v)     }   }   loop_filter_across_tiles_enabled_flag u(1)   loop_filter_across_slices_enabled_flag u(1)  }  entropy_coding_sync_enabled_flag u(1)  if( !no_pic_partition_flag | | entropy_coding_sync_enabled_ flag )   entry_point_offsets_present_flag u(1)  ...  }

With respect to Table 2, the semantics of syntax elements may be based on the semantics provided above with respect to Table 1, with the semantics of syntax element tile_idx_delta_present_flag, in one example, based on the following: tile_idx_delta_present_flag equal to 0 specifies that tile_idx_delta values are not present in the PPS and that all rectangular slices in pictures referring to the PPS are specified in raster order according to the process defined above. tile_idx_delta_present_flag equal to 1 specifies that tile_idx_delta values may be present in the PPS and that all rectangular slices in pictures referring to the PPS are specified in the order indicated by the values of tile_idx_delta. When not present tile_idx_delta_present_flag is inferred to be equal to 0.

In another example, the syntax element tile_idx_delta_present_flag may instead be signaled as a tile_idx_delta not present flag. In this case, the value for the syntax element may be inferred to be equal to 1 when not present.

In one example, according to the techniques herein, syntax element indicating whether each rectangular slice consists of exactly one tile, e.g., single_tile_per_slice_flag, may be signaled, conditionally or unconditionally, to avoid signaling many syntax elements for this relatively common case. This provides bit-savings. Tables 3A-3C illustrate examples of the relevant portion of the syntax structure of a picture parameter set syntax structure where a syntax element single_tile_per_slice_flag is signaled, according to the techniques herein. It should be noted that in Table 3A, syntax element single_tile_per_slice_flag is signaled only when single_slice_per_subpic_flag is not equal to 1, in Table 3B, syntax element single_tile_per_slice_flag is unconditionally signaled, and in Table 3C, syntax element single_tile_per_slice_flag is signaled only for rectangular slices and only when single_slice_per_subpic_flag is not equal to 1.

TABLE 3A Descriptor pic_parameter_set_rbsp( ) {  pps_pic_parameter_set_id ue(v)  pps_seq_parameter_set_id u(4)  pps_seq_parameter_set_id ue(v)  pic_width_in_luma_samples ue(v)  pic_height_in_luma_samples ue(v)  conformance_window_flag u(1)  if( conformance_window_flag ) {   conf_win_left_offset ue(v)   conf_win_right_offset ue(v)   conf_win_top_offset ue(v)   conf_win_bottom_offset ue(v)  }  scaling_window_flag u(1)  if( scaling_window_flag ) {   scaling_win_left_offset ue(v)   scaling_win_right_offset ue(v)   scaling_win_top_offset ue(v)   scaling_win_bottom_offset ue(v)  }  output_flag_present_flag u(1)  mixed_nalu_types_in_pic_flag u(1)  pps_subpic_id_signalling_present_flag u(1)  if( pps_subpics_id_signalling_present_flag ) {   pps_num_subpics_minus1 ue(v)   pps_subpic_id_len_minus1 ue(v)   for( i = 0; i <= pps_num_subpic_minus1; i++ )    pps_subpic_id[ i ] u(v)  }  no_pic_partition_flag u(1)  if( !no_pic_partition_flag ) {   pps_log2_ctu_size_minus5 u(2)   num_exp_tile_columns_minus1 ue(v)   num_exp_tile_rows_minus1 ue(v)   for( i = 0; i <= num_exp_tile_columns_minus1; i++ )    tile_column_width_minus1[ i ] ue(v)   for(i = 0; i <= num_exp_tile_rows_minus1; i++ )    tile_row_height_minus1[ i ] ue(v)   rect_slice_flag u(1)   if( rect_slice_flag) {    single_slice_per_subpic_flag u(1)    if(! single_slice_per_subpic_flag)     single_tile_per_slice_flag u(1)     }   if( rect_slice_flag && !single_slice_per_subpic_flag && ! single_tile_per_slice_flag ) {    num_slices_in_pic_minus1 ue(v)     tile_idx_delta_present_flag u(1)    for( i = 0; i < num_slices_in_pic_minus1; i++ ) {     slice_width_in_tiles_minus1[ i ] ue(v)     slice_height_in_tiles_minus1[ i ] ue(v)     if( slice_width_in_tiles_minus1 [ i ] == 0 &&        slice_height_in_tiles_minus1[ i ] == 0 ) {      num_slices_in_tile_minus1[ i ] ue(v)      numSlicesInTileMinus1 = num_slices_in_tile_ minus1[ i ]      for( j = 0; j < numSlicesInTileMinus1; j++ )       slice_height_in_ctu_minus1[ i++ ] ue(v)     }     if( tile_idx_delta_present_flag && i < num_ slices_in_pic_minus1 )      tile_idx_delta[ i ] se(v)    }   }   loop_filter_across_tiles_enabled_flag u(1)   loop_filter_across_slices_enabled_flag u(1)  }  entropy_coding_sync_enabled_flag u(1)  if( !no_pic_partition_flagentropy_coding_sync_enabled_flag )   entry_point_offsets_present_flag u(1)  ...  }

TABLE 3B Descriptor pic_parameter_set_rbsp( ) {  pps_pic_parameter_set_id ue(v)  pps_seq_parameter_set_id u(4)  pps_seq_parameter_set_id ue(v)  pic_width_in_luma_samples ue(v)  pic_height_in_luma_samples ue(v)  conformance_window_flag u(1)  if( conformance_window_flag ) {   conf_win_left_offset ue(v)   conf_win_right_offset ue(v)   conf_win_top_offset ue(v)   conf_win_bottom_offset ue(v)  }  scaling_window_flag u(1)  if( scaling_window_flag) {   scaling_win_left_offset ue(v)   scaling_win_right_offset ue(v)   scaling_win_top_offset ue(v)   scaling_win_bottom_offset ue(v)  }  output_flag_present_flag u(1)  mixed_nalu_types_in_pic_flag u(1)  pps_subpic_id_signalling_present_flag u(1)  if( pps_subpics_id_signalling_present_flag) {   pps_num_subpics_minus1 ue(v)   pps_subpic_id_len_minus1 ue(v)   for( i = 0; i <= pps_num_subpic_minus1; i++ )    pps_subpic_id[ i ] u(v)  }  no_pic_partition_flag u(1)  if( !no_pic_partition_flag ) {   pps_log2_ctu_size_minus5 u(2)   num_exp_tile_columns_minus1 ue(v)   num_exp_tile_rows_minus1 ue(v)   for( i = 0; i <= num_exp_tile_columns_minus1; i++ )    tile_column_width_minus1[ i ] ue(v)   for(i = 0; i <= num_exp_tile_rows_minus1; i++ )    tile_row_height_minus1[ i ] ue(v)   rect_slice_flag u(1)   if( rect_slice_flag )    single_slice_per_subpic_flag u(1)    single_tile_per_slice_flag u(1)   if( rect_slice_flag && !single_slice_per_subpic_flag && !single_tile_per_slice_flag ) {    num_slices_in_pic_minus1 ue(v)     tile_idx_delta_present_flag u(1)    for( i = 0; i < num_slices_in_pic_minus1; i++ ) {     slice_width_in_tiles_minus1[ i ] ue(v)     slice_height_in_tiles_minus1[ i ] ue(v)     if( slice_width_in_tiles_minus1[ i ] ==  0 &&        slice_height_in_tiles_minus1[ i ] == 0 ) {     num_slices_in_tile_minus1[ i ] ue(v)     numSlicesInTileMinus1 = num_slices_in_tile_ minus1[ i ]     for( j = 0; j < numSlicesInTileMinus1; j++ )       slice_height_in_ctu_minus1[ i++ ] ue(v)     }     if( tile_idx_delta_present_flag && i < num_slices_ in_pic_minus1 )      tile_idx_delta[ i ] se(v)    }   }   loop_filter_across_tiles_enabled_flag u(1)   loop_filter_across_slices_enabled_flag u(1)  }  entropy_coding_sync_enabled_flag u(1)  if( !no_pic_partition_flag | | entropy_coding_sync_ enabled_flag )   entry_point_offsets_present_flag u(1)  ...  }

TABLE 3C Descriptor pic_parameter_set_rbsp( ) {  pps_pic_parameter_set_id ue(v)  pps_seq_parameter_set_id u(4)  pps_seq_parameter_set_id ue(v)  pic_width_in_luma_samples ue(v)  pic_height_in_luma_samples ue(v)  conformance_window_flag u(1)  if( conformance_window_flag) {   conf_win_left_offset ue(v)   conf_win_right_offset ue(v)   conf_win_top_offset ue(v)   conf_win_bottom_offset ue(v)  }  scaling_window_flag u(1)  if( scaling_window_flag ) {   scaling_win_left_offset ue(v)   scaling_win_right_offset ue(v)   scaling_win_top_offset ue(v)   scaling_win_bottom_offset ue(v)  }  output_flag_present_flag u(1)  mixed_nalu_types_in_pic_flag u(1)  pps_subpic_id_signalling_present_flag u(1)  if( pps_subpics_id_signalling_present_flag ) {   pps_num_subpics_minus1 ue(v)   pps_subpic_id_len_minus1 ue(v)   for( i = 0; i <= pps_num_subpic_minus1; i++)    pps_subpic_id[ i ] u(v)  }  no_pic_partition_flag u(1)  if( !no_pic_partition_flag ) {   pps_log2_ctu_size_minus5 u(2)   num_exp_tile_columns_minus1 ue(v)   num_exp_tile_rows_minus1 ue(v)   for(i = 0; i <= num_exp_tile_columns_minus1; i++)    tile_column_width_minus1[ i ] ue(v)   for( i = 0; i <= num_exp_tile_rows_minus1: i++ )    tile_row_height_minus1[ i ] ue(v)   rect_slice_flag u(1)   if( rect_slice_flag) {    single_tile_per_slice_flag u(1)   if(!single_tile_per_slice_flag)    single_slice_per_subpic_flag u(1)   }   if(rect_slice_flag &&, !single_slice_per_subpic_flag && !single_tile_per_slice_flag )  {   num_slices_in_pic_minus1 ue(v)    tile_idx_delta_present_flag u(1)   for( i = 0; i < num_slices_in_pic_minus1; i++ ) {    slice_width_in_tiles_minus1[ i ] ue(v)    slice_height_in_tiles_minus1[ i ] ue(v)    if( slice_width_in_tiles_minus1[ i ]  == 0 &&       slice_height_in_tiles_minus1[ i ] == 0 ) {     num_slices_in_tile_minus1[ i ] ue(v)     numSlicesInTileMinus1 = num_slices_in_tile_ minus1 [ i ]     for( j = 0; j < numSlicesInTileMinus1; j++ )      slice_height_in_ctu_minus1[ i++ ] ue(v)     }     if( tile_idx_delta_present_flag && i < num_ slices_in_pic_minus1 )     tile_idx_delta[ i ] se(v)    }   }   loop_filter_across_tiles_enabled_flag u(1)   loop_filter_across_slices_enabled_flag u(1)  }  entropy_coding_sync_enabled_flag u(1)  if( !no_pic_partition_flag | | entropy_coding_sync_ enabled_flag )   entry_point_offsets_present_flag u(1)  ...  }

With respect to Tables 3A-3C, the semantics of syntax elements may be based on the semantics provided above with respect to Table 1, with the semantics of syntax element single_tile_per_slice_flag, in one example, based on the following:

single_tile_per_slice_flag equal to 1 specifies that each rectangular slice consists of exactly one tile. single_tile_per_slice_flag equal to 0 specifies that each rectangular slice consists of one or more tiles. When single_tile_per_slice_flag is equal to 1, num_slices_in_pic_minus1 is inferred to be equal to NumTiles−1. When not present single_tile_per_slice_flag is inferred to be equal to 0.

With respect to Table 3B, single_tile_per_slice_flag may be signalled for nonrectangular slices (or raster-scan slices) in addition, to for rectangular slices.

With respect to Tables 3A-3C, in one example, according to the techniques herein, a corresponding process for scanning may be based on the following:

For rectangular slices, the list NumCtuInSlice[i] for i ranging from 0 to num_slices_in_pic_minus1, inclusive, specifying the number of CTU in the i-th slice, and the matrix CtbAddrInSlice[i][j] for i ranging from 0 to num_slices_in_pic_minus1, inclusive, and j ranging from 0 to NumCtuInSlice[i]−1, inclusive, specifying the picture raster scan address of the j-th CTB within the i-th slice, are derived as follows:

if( subpics_present_flag && single_slice_per_subpic_flag ) {  for( i = 0; i <= sps_num_subpics_minus1; i++ )   NumCtulnSlice[ i ] = 0  for( i = 0; i < PicSizeInCtbsY; i ++ ) {   sliceIdx = CtbToSubPicIdx[ i ]   CtbAddrInSlice[ sliceIdx ][ NumCtuInSlice[ sliceIdx ] ] = i   NumCtuInSlice[ sliceIdx ]++  } } else if (single_tile_per_slice_flag) {  for( i = 0; i < NumTilesInPic; i++ )   NumCtuInSlice[ i ] = 0  for( i = 0; i < NumTilesInPic; i++ ) {    tileX = i % NumTileColumns    tileY = i / NumTileColumns    AddCtbsToSlice(i, tileColBdf tileX ], tileColBd[ tileX + 1 ], tileRowBd tileY ], tileRowBd[ tileY + 1 ] )  } }else {  tileIdx = 0  for( i = 0; i <= num_slices_in_pic_minus1; i++ )   NumCtuInSlice[ i ] = 0  for( i = 0; i <= num_slices_in_pic_minus1; i++ ) {   tileX = tileIdx % NumTileColumns   tileY = tileIdx / NumTileColumns   if( i = = num_slices_in_pic_minus1) {    slice_width_in_tiles_minus1 [ i ] = NumTileColumns − 1 − tileX    slice_height_in_tiles_minus1[ i ] = NumTileRows − 1 − tileY    num_slices_in_tile_minus1[ i ] = 0   }   if( slice_width_in_tiles_minus 1 [ i ] = = 0 && slice_height_in_tiles_minus1[ i ] = = 0 ) {    ctbY = tileRowBd tileY ]    numSlicesInTileMinus1 = num_slices_in_tile_minus 1[ i ]    for( j = 0; j < numSlicesInTileMinus1; j++ ) {     AddCtbsToSlice( i, tileColBd[ tileX ], tileColBd[ tileX + 1 ],       ctbY, ctbY + slice_height_in_ctu_minus1 [ i ] + 1 )     ctbY += slice_height_in_ctu_minus 1 [ i ] + 1     i++    }    AddCtbsToSlice( i, tileColBd[ tileX ], tileColBd[ tileX + 1 ], ctbY, tileRowBd[ tileY + 1 ])   } else    for( j = 0; j <= slice_height_in_tiles_minus1[ i ]; j++ )     for( k = 0; k <= slice_width_in_tiles_minus1[ i ]; k++ )      AddCtbsToSlice( i, tileColBd[ tileX + k ], tileColBd[ tileX + k + 1 ]       tileRowBd[ tileY + j ], tileRowBd tileY + j + 1 ] )   if( tile_idx_delta_present_flag )    tileIdx += tile_idx_delta[ i ]   else {    tileIdx += slice_width_in_tiles_minus1[ i ] + 1    if( tileIdx % NumTileColumns = = 0 )     tileIdx += slice_height_in_tiles_minus1[ i ]* NumTileColumns   }  } }

-   -   Where the function AddCtbsToSlice(sliceIdx, startX, stopX,         startY, stopY) is specified as follows:

for( ctbY = startY; ctbY < stopY; ctbY++ )  for( ctbX = startX; ctbX < stopX; ctbX++ ) {   CtbAddrInSlice[ sliceIdx ][ NumCtuInSlice[ sliceIdx ] ] = ctbY * PicWidthInCtbsY + ctbX   NumCtuInSlice[ sliceIdx ]++  }

It should be noted that in other examples, syntax element single_tile_per_slice_flag may be referred to as single slice per tile flag or by some other name. In another example, a separate flag single_tile_per_slice_flag[i] may be signalled for each tile or for each slice or for each subpicture.

In one example, according to the techniques herein, inference rules are specified for syntax element single_slice_per_subpic_flag when it is not present. It should be noted that the flag single_slice_per_subpic_flag is used in the conditioning of syntax elements in a picture parameter set and also in the derivation of CTB raster scanning, tile scanning, and subpicture scanning processes provided above. Tables 4A-4B illustrate examples of the relevant portion of the syntax structure of a picture parameter set syntax structure where syntax elements are conditionally signaled based on the value of syntax element single_slice_per_subpic_flag according to the techniques herein.

TABLE 4A Descriptor pic_parameter_set_rbsp( ) {  pps_pic_parameter_set_id ue(v)  pps_seq_parameter_set_id u(4)  pps_seq_parameter_set_id ue(v)  pic_width_in_luma_samples ue(v)  pic_height_in_luma_samples ue(v)  conformance_window_flag u(1)  if( conformance_window_flag ) {   conf_win_left_offset ue(v)   conf_win_right_offset ue(v)   conf_win_top_offset ue(v)   conf_win_bottom_offset ue(v)  }  scaling_window_flag u(1)  if( scaling_window_flag ) {   scaling_win_left_offset ue(v)   scaling_win_right_offset ue(v)   sealing_win_top_offset ue(v)   scaling_win_bottom_offset ue(v)  }  output_flag_present_flag u(1)  mixed_nalu_types_in_pic_flag u(1)  pps_subpic_id_signalling_present_flag u(1)  if( pps_subpics_id_signalling_present_flag ) {   pps_num_subpics_minus1 ue(v)   pps_subpic_id_len_minus1 ue(v)   for( i = 0; i <= pps_num_subpic_minus1; i++ )    pps_subpic_id[ i ] u(v)  }  no_pic_partition_flag u(1)  if( !no_pic_partition_flag ) {   pps_log2_ctu_size_minus5 u(2)   num_exp_tile_columns_minus1 ue(v)   num_exp_tile_rows_minus1 ue(v)   for( i = 0; i <= num_exp_tile_columns_minus 1; i++ )    tile_column_width_minus1[ i ] ue(v)   for( i = 0; i <= num_exp_tile_rows_minus1: i++ )    tile_row_height_minus1[ i ] ue(v)   rect_slice_flag u(1)   if( rect_slice_flag)    single_slice_per_subpic_flag u(1)   if( rect_slice_flag && !single_slice_per_subpic_flag ) {    num_slices_in_pic_minus1 ue(v)     tile_idx_delta_present_flag u(1)    for( i = 0; i < num_slices_in_pic_minus1; i++ ) {     slice_width_in_tiles_minus1[ i ] ue(v)     slice_height_in_tiles_minus1[ i ] ue(v)     if( slice_width_in_tiles_minus1[ i ] == 0 &&        slice height_in_tiles_minus1[ i ] == 0 ) {      num_slices_in_tile_minus1[ i ] ue(v)      numSlicesInTileMinus1 = num_slices_in_tile_ minus1[ i ]      for(j = 0; j < numSlicesInTileMinus1; j++ )       slice_height_in_ctu_minus1[ i++] ue(v)     }     if( tile_idx_delta_present_flag && i < num_ slices_in_pic_minus1 )      tile_idx_delta[ i ] se(v)    }   }   loop_filter_across_tiles_enabled_flag u(1)   loop_filter_across_slices_enabled_flag u(1)  }  entropy_coding_sync_enabled_flag u(1)  if(!no_pic_partition_flag | | entropy_coding_sync_ enabled_flag )   entry_point_offsets_present_flag u(1)  ...  }

TABLE 4B Descriptor pic_parameter_set_rbsp( ) {  pps_pic_parameter_set_id ue(v)  pps_seq_parameter_set_id u(4)  pps_seq_parameter_set_id ue(v)  pic_width_in_luma_samples ue(v)  pic_height_in_luma_samples ue(v)  conformance_window_flag u(1)  if( conformance_window_flag ) {   conf_win_left_offset ue(v)   conf_win_right_offset ue(v)   conf_win_top_offset ue(v)   conf_win_bottom_offset ue(v)  }  scaling_window_flag u(1)  if( scaling_window_flag ) {   scaling_win_left_offset ue(v)   scaling_win_right_offset ue(v)   scaling_win_top_offset ue(v)   scaling_win_bottom_offset ue(v)  }  output_flag_present_flag u(1)  mixed_nalu_types_in_pic_flag u(1)  pps_subpic_id_signalling_present_flag u(1)  if( pps_subpics_id_signalling_present_flag ) {   pps_num_subpics_minus1 ue(v)   pps_subpic_id_len_minus1 ue(v)   for( i = 0; i <= pps_num_subpic_minus1; i++ )    pps_subpic_id[ i ] u(v)  }  no_pic_partition_flag u(1)  if( !no_pic_partition_flag ) {   pps_log2_ctu_size_minus5 u(2)   num_exp_tile_columns_minus1 ue(v)   num_exp_tile_rows_minus1 ue(v)   for(i = 0;i <= num_exp_tile_columns_minus1; i++ )    tile_column_width_minus1[ i ] ue(v)   for( i = 0; i <= num_exp_tile_rows_minus1; i++ )    tile_row_height_minus1[ i ] ue(v)   rect_slice_flag u(1)   if( rect_slice_flag ) {    single_slice_per_subpic_flag u(1)   if( !single_slice_per_subpic_flag ) {    num_slices_in_pic_minus1 ue(v)     tile_idx_delta_present_flag u(1)    for( i = 0; i < num_slices_in_pic_minus1; i++ ) {     slice_width_in_tiles_minus1[ i ] ue(v)     slice_height_in_tiles_minus1[ i ] ue(v)     if( slice_width_in_tiles_minus1[ i ] == 0 &&        slice_height_in_tiles_minus1[ i ] == 0 ){      num_slices_in_tile_minus1[ i ] ue(v)      numSlicesInTileMinus1 = num_slices_in_ tile_minus1[ i ]      for( j = 0; j < numSlicesInTileMinus1; j++ )       slice_height_in_ctu_minus1[ i++ ] ue(v)     }     if( tile_idx_delta_present_flag && i < num_ slices_in_pic_minus1 )      tile_idx_delta[ i ] se(v)    }   }  }   loop_filter_across_tiles_enabled_flag u(1)   loop_filter_across_slices_enabled_flag u(1)  }  entropy_coding_sync_enabled_flag u(1)  if( !no_pic_partition_flag | | entropy_coding_sync_ enabled_flag )   entry_point_offsets_present_flag u(1)  ...  }

With respect to Tables 4A-4B, the semantics of syntax elements may be based on the semantics provided above with respect to Table 1, with the semantics of syntax element single_slice_per_subpic_flag in one example, based on the following:

single_slice_per_subpic_flag equal to 1 specifies that each subpicture consists of one and only one rectangular slice. single_slice_per_subpic_flag equal to 0 specifies that each subpicture may consist one or more rectangular slices. When subpics_present_flag is equal to 0, single_slice_per_subpic_flag shall be equal to 0. When single_slice_per_subpic_flag is equal to 1, num_slices_in_pic_minus1 is inferred to be equal to sps_num_subpics_minus1. When not present single_slice_per_subpic_flag is inferred to be equal to 0.

In this manner, source device 102 represents an example of a device configured to signal a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally signal one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

Referring again to FIG. 1 , interface 108 may include any device configured to receive data generated by data encapsulator 107 and transmit and/or store the data to a communications medium. Interface 108 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can send and/or receive information. Further, interface 108 may include a computer system interface that may enable a file to be stored on a storage device. For example, interface 108 may include a chipset supporting Peripheral Component Interconnect (PCI) and Peripheral Component Interconnect Express (PCIe) bus protocols, proprietary bus protocols, Universal Serial Bus (USB) protocols, I²C, or any other logical and physical structure that may be used to interconnect peer devices.

Referring again to FIG. 1 , destination device 120 includes interface 122, data decapsulator 123, video decoder 124, and display 126. Interface 122 may include any device configured to receive data from a communications medium. Interface 122 may include a network interface card, such as an Ethernet card, and may include an optical transceiver, a radio frequency transceiver, or any other type of device that can receive and/or send information. Further, interface 122 may include a computer system interface enabling a compliant video bitstream to be retrieved from a storage device. For example, interface 122 may include a chipset supporting PCI and PCIe bus protocols, proprietary bus protocols, USB protocols, I²C, or any other logical and physical structure that may be used to interconnect peer devices. Data decapsulator 123 may be configured to receive and parse any of the example syntax structures described herein.

Video decoder 124 may include any device configured to receive a bitstream (e.g., a sub-bitstream extraction) and/or acceptable variations thereof and reproduce video data therefrom. Display 126 may include any device configured to display video data. Display 126 may comprise one of a variety of display devices such as a liquid crystal display (LCD), a plasma display, an organic light emitting diode (OLED) display, or another type of display. Display 126 may include a High Definition display or an Ultra High Definition display. It should be noted that although in the example illustrated in FIG. 1 , video decoder 124 is described as outputting data to display 126, video decoder 124 may be configured to output video data to various types of devices and/or subcomponents thereof. For example, video decoder 124 may be configured to output video data to any communication medium, as described herein.

FIG. 6 is a block diagram illustrating an example of a video decoder that may be configured to decode video data according to one or more techniques of this disclosure (e.g., the decoding process for reference-picture list construction described above). In one example, video decoder 600 may be configured to decode transform data and reconstruct residual data from transform coefficients based on decoded transform data. Video decoder 600 may be configured to perform intra prediction decoding and inter prediction decoding and, as such, may be referred to as a hybrid decoder. Video decoder 600 may be configured to parse any combination of the syntax elements described above in Tables 1-4B. Video decoder 600 may decode a picture based on or according to the processes described above, and further based on parsed values in Tables 1-4B.

In the example illustrated in FIG. 6 , video decoder 600 includes an entropy decoding unit 602, inverse quantization unit and transform coefficient processing unit 604, intra prediction processing unit 606, inter prediction processing unit 608, summer 610, post filter unit 612, and reference buffer 614. Video decoder 600 may be configured to decode video data in a manner consistent with a video coding system. It should be noted that although example video decoder 600 is illustrated as having distinct functional blocks, such an illustration is for descriptive purposes and does not limit video decoder 600 and/or sub-components thereof to a particular hardware or software architecture. Functions of video decoder 600 may be realized using any combination of hardware, firmware, and/or software implementations.

As illustrated in FIG. 6 , entropy decoding unit 602 receives an entropy encoded bitstream. Entropy decoding unit 602 may be configured to decode syntax elements and quantized coefficients from the bitstream according to a process reciprocal to an entropy encoding process. Entropy decoding unit 602 may be configured to perform entropy decoding according any of the entropy coding techniques described above. Entropy decoding unit 602 may determine values for syntax elements in an encoded bitstream in a manner consistent with a video coding standard. As illustrated in FIG. 6 , entropy decoding unit 602 may determine a quantization parameter, quantized coefficient values, transform data, and predication data from a bitstream. In the example, illustrated in FIG. 6 , inverse quantization unit and transform coefficient processing unit 604 receives a quantization parameter, quantized coefficient values, transform data, and predication data from entropy decoding unit 602 and outputs reconstructed residual data.

Referring again to FIG. 6 , reconstructed residual data may be provided to summer 610 Summer 610 may add reconstructed residual data to a predictive video block and generate reconstructed video data. A predictive video block may be determined according to a predictive video technique (i.e., intra prediction and inter frame prediction). Intra prediction processing unit 606 may be configured to receive intra prediction syntax elements and retrieve a predictive video block from reference buffer 614. Reference buffer 614 may include a memory device configured to store one or more frames of video data. Intra prediction syntax elements may identify an intra prediction mode, such as the intra prediction modes described above. Inter prediction processing unit 608 may receive inter prediction syntax elements and generate motion vectors to identify a prediction block in one or more reference frames stored in reference buffer 616. Inter prediction processing unit 608 may produce motion compensated blocks, possibly performing interpolation based on interpolation filters. Identifiers for interpolation filters to be used for motion estimation with sub-pixel precision may be included in the syntax elements. Inter prediction processing unit 608 may use interpolation filters to calculate interpolated values for sub-integer pixels of a reference block. Post filter unit 614 may be configured to perform filtering on reconstructed video data. For example, post filter unit 614 may be configured to perform deblocking and/or Sample Adaptive Offset (SAO) filtering, e.g., based on parameters specified in a bitstream. Further, it should be noted that in some examples, post filter unit 614 may be configured to perform proprietary discretionary filtering (e.g., visual enhancements, such as, mosquito noise reduction). As illustrated in FIG. 6 , a reconstructed video block may be output by video decoder 600. In this manner, video decoder 600 represents an example of a device configured to parse a syntax element indicating whether each rectangular slice consists of exactly one tile and conditionally parse one or more syntax elements indicating a number of slices in a picture based on the value of the syntax element indicating whether each rectangular slice consists of exactly one tile.

In one or more examples, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium and executed by a hardware-based processing unit. Computer-readable media may include computer-readable storage media, which corresponds to a tangible medium such as data storage media, or communication media including any medium that facilitates transfer of a computer program from one place to another, e.g., according to a communication protocol. In this manner, computer-readable media generally may correspond to (1) tangible computer-readable storage media which is non-transitory or (2) a communication medium such as a signal or carrier wave. Data storage media may be any available media that can be accessed by one or more computers or one or more processors to retrieve instructions, code and/or data structures for implementation of the techniques described in this disclosure. A computer program product may include a computer-readable medium.

By way of example, and not limitation, such computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage, or other magnetic storage devices, flash memory, or any other medium that can be used to store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if instructions are transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. It should be understood, however, that computer-readable storage media and data storage media do not include connections, carrier waves, signals, or other transitory media, but are instead directed to non-transitory, tangible storage media. Disk and disc, as used herein, includes compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Instructions may be executed by one or more processors, such as one or more digital signal processors (DSPs), general purpose microprocessors, application specific integrated circuits (ASICs), field programmable logic arrays (FPGAs), or other equivalent integrated or discrete logic circuitry. Accordingly, the term “processor,” as used herein may refer to any of the foregoing structure or any other structure suitable for implementation of the techniques described herein. In addition, in some aspects, the functionality described herein may be provided within dedicated hardware and/or software modules configured for encoding and decoding, or incorporated in a combined codec. Also, the techniques could be fully implemented in one or more circuits or logic elements.

The techniques of this disclosure may be implemented in a wide variety of devices or apparatuses, including a wireless handset, an integrated circuit (IC) or a set of ICs (e.g., a chip set). Various components, modules, or units are described in this disclosure to emphasize functional aspects of devices configured to perform the disclosed techniques, but do not necessarily require realization by different hardware units. Rather, as described above, various units may be combined in a codec hardware unit or provided by a collection of interoperative hardware units, including one or more processors as described above, in conjunction with suitable software and/or firmware.

Moreover, each functional block or various features of the base station device and the terminal device used in each of the aforementioned embodiments may be implemented or executed by a circuitry, which is typically an integrated circuit or a plurality of integrated circuits. The circuitry designed to execute the functions described in the present specification may comprise a general-purpose processor, a digital signal processor (DSP), an application specific or general application integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, or a discrete hardware component, or a combination thereof. The general-purpose processor may be a microprocessor, or alternatively, the processor may be a conventional processor, a controller, a microcontroller or a state machine. The general-purpose processor or each circuit described above may be configured by a digital circuit or may be configured by an analogue circuit. Further, when a technology of making into an integrated circuit superseding integrated circuits at the present time appears due to advancement of a semiconductor technology, the integrated circuit by this technology is also able to be used.

Various examples have been described. These and other examples are within the scope of the following claims.

CROSS REFERENCE

This Nonprovisional application claims priority under 35 U.S.C. § 119 on provisional Application No. 62/939,451 on Nov. 22, 2019, the entire contents of which are hereby incorporated by reference. 

1. A method of encoding video data, the method comprising: signaling a first syntax element specifying whether each subpicture consists of one and only one rectangular slice, or each subpicture consists one or more rectangular slices; signaling a second syntax element specifying a number of rectangular slices in each picture referring to a picture parameter set in a case that the first syntax element specifies that each subpicture consists one or more rectangular slices; determining whether or not a third syntax element is to be signaled based on the second syntax element; signaling the third syntax element, specifying whether or not fourth syntax elements are present in the picture parameter set, based on the second syntax element; and signaling the fourth syntax elements, specifying a difference in indexes between two rectangular slices, based on the second syntax element and the third syntax element.
 2. A method of decoding video data, the method comprising: decoding a first syntax element specifying whether each subpicture consists of one and only one rectangular slice, or each subpicture consists one or more rectangular slices; decoding a second syntax element specifying a number of rectangular slices in each picture referring to a picture parameter set in a case that the first syntax element specifies that each subpicture consists one or more rectangular slices; determining whether or not a third syntax element is to be decoded based on the second syntax element; decoding a third syntax element, specifying whether or not fourth syntax elements are present in the picture parameter set, based on the second syntax element; and decoding the fourth syntax elements, specifying a difference in indexes between two rectangular slices, based on the second syntax element and the third syntax element.
 3. The method of claim 2, wherein, when the third syntax element is not present, a value of the third syntax element is inferred to be equal to
 0. 